Announcement

Collapse
No announcement yet.

pkcon update error message

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] pkcon update error message

    I've been using the pkcon refresh and update commands to update my hybrid Neon (with Kubuntu 16.04) and I keep getting this error message:

    (pkcon:10564): GLib-CRITICAL **: Source ID 158 was not found when attempting to remove it

    What does it mean? It does not seem to have any effect on the functioning of the OS.

    #2
    You can use "ps -e" to see a list of process IDs.
    "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
    – John F. Kennedy, February 26, 1962.

    Comment


      #3
      It can be ignored, and can be seen sort of as terminal spam of sorts.
      It seems many programs (from what I saw running search queries on this) show this message when run in a terminal.

      Comment


        #4
        kworker is the process associated with ID 158. Whatever that is.

        Comment


          #5
          kworker is a kernel worker process.
          https://unix.stackexchange.com/quest...er/65270#65270

          What is your output of
          sudo cat /proc/158/stack


          Also,
          https://askubuntu.com/questions/1765...ge-get-so-high
          Last edited by GreyGeek; Jun 23, 2017, 03:37 PM.
          "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
          – John F. Kennedy, February 26, 1962.

          Comment


            #6
            The message is garbage output and can safely be ignored.
            It is an output from the glib library :

            This isn't a bug in your code, and it's not a crash either. It's actually just a warning that g_source_remove() was called to disconnect a certain event handler that was already disconnected, in this case, in code that is part of gtk.

            The warning itself was introduced in glib 2.39, in this commit,

            ....


            In most cases this is completely harmless, and only an annoyance
            Which is the least confusing but no less over-my-head explanation I could find.

            Comment


              #7
              Fine. I keep getting messages with new IDs but since they don't affect anything that I can see so far I will just ignore them. Thanks.

              Comment

              Working...
              X