GNOME Bugzilla – Bug 721369
GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
Last modified: 2021-05-26 09:19:37 UTC
Forward bug upstream from Ubuntu... https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1264368 Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it The warning is also sent to /var/log/syslog Other Info: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)
You're using a version of glib targeted for GNOME 3.12 with GNOME 3.6. That's really not supported. Please test with a newer version, and provide a backtrace of the warning (run gnome-control-center with the G_DEBUG=fatal_criticals environment variable).
Hi, Maybe I am off topic, and I am sorry if I do ! (please let me know) but I get the same error message when lauching gparted from terminal, ubuntu 14.04, i386 GLib-CRITICAL **: Source ID xxx was not found when attempting to remove it About 40 lines with the same warning ; only the xxx number change. Does it mean that this warning does NOT come from gnome-control-center ? Larry
Same result after updating : Package: libglib2.0-0 Architecture: i386 Version: 2.39.91-0ubuntu2
This happens also with vim-gtk in Debian, using glib 2.40
(In reply to comment #2) > Hi, > Maybe I am off topic, and I am sorry if I do ! > (please let me know) > but I get the same error message when lauching gparted from terminal, ubuntu > 14.04, i386 > GLib-CRITICAL **: Source ID xxx was not found when attempting to remove it > About 40 lines with the same warning ; only the xxx number change. > > Does it mean that this warning does NOT come from gnome-control-center ? Absolutely not. (In reply to comment #4) > This happens also with vim-gtk in Debian, using glib 2.40 And also absolutely not. The warnings come from misuse of g_source_remove() in either the application or the dependent libraries. If vim-gtk or gparted throw warnings, then they're broken.
> (In reply to comment #4) > > This happens also with vim-gtk in Debian, using glib 2.40 Yeah, I wasn't implying it'd come from gnome-control-center which I don't use, I was more thinking about a but in glib or gtk+ > > And also absolutely not. > > The warnings come from misuse of g_source_remove() in either the application or > the dependent libraries. If vim-gtk or gparted throw warnings, then they're > broken. Considering the fact that multiple application seem impacted, I'd think of a dependent library (wether gtk+ or something else). A search for g_source_remove(): http://codesearch.debian.net/search?q=g_source_remove Shows a lot of stuff. Especially glib and gtk+, but there's also avahi, pulseaudio, dbus-glib, policykit, bluez, gconf, libsoup (which look unrelated), but maybe more. So it's actually not that easy to identify that lib, but I'd guess gtk+.
(In reply to comment #6) > > (In reply to comment #4) > > > This happens also with vim-gtk in Debian, using glib 2.40 > > Yeah, I wasn't implying it'd come from gnome-control-center which I don't use, > I was more thinking about a but in glib or gtk+ > > > > And also absolutely not. > > > > The warnings come from misuse of g_source_remove() in either the application or > > the dependent libraries. If vim-gtk or gparted throw warnings, then they're > > broken. > > Considering the fact that multiple application seem impacted, I'd think of a > dependent library (wether gtk+ or something else). > > A search for g_source_remove(): > > http://codesearch.debian.net/search?q=g_source_remove > > Shows a lot of stuff. Especially glib and gtk+, but there's also avahi, > pulseaudio, dbus-glib, policykit, bluez, gconf, libsoup (which look unrelated), > but maybe more. So it's actually not that easy to identify that lib, but I'd > guess gtk+. It's not GTK+. GLib recently started throwing a warning when g_source_remove() is passed garbage (as per warning). Your applications have probably been broken for a while, and there's no telling what could actually have happened in the past when g_source_remove() would happily close any random source because the programmer got the wrong argument to g_source_remove().
I suspect this is not just an innocent warning. From my PoV, it is a serious regression that was introduced recently. I recently upgraded Ubuntu from 13.10 to 14.04 On the day of the upgrade some of my ssh sessions started to hang. So I note down the second they hang, re-ssh, and look at /var/log/syslog At exactly the same second of the ssh session hang (example: 12:48:29) I find this matching event in the logs: Apr 25 12:48:29 xxxx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 3130 was not found when attempting to remove it Apr 25 12:48:29 xxxx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 3130 was not found when attempting to remove it Apr 25 12:48:29 xxxx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 3162 was not found when attempting to remove it They always come in triplets at the same second, and they are always (for me and console-kit-daemon anyhow) indicate a real issue that was not there before I started getting the errors. So whoever made the change to the code to start handling this error case may have also changed some semantics that cause dependent applications to break. Thank you for giving more attention to this bug.
(In reply to comment #8) > I suspect this is not just an innocent warning. > From my PoV, it is a serious regression that was introduced recently. It's not. > I recently upgraded Ubuntu from 13.10 to 14.04 > > On the day of the upgrade some of my ssh sessions started to hang. It has nothing to do with the warning in the control-center Network panel. > So I note down the second they hang, re-ssh, and look at /var/log/syslog > At exactly the same second of the ssh session hang (example: 12:48:29) I find > this matching event in the logs: > > Apr 25 12:48:29 xxxx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 3130 > was not found when attempting to remove it > Apr 25 12:48:29 xxxx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 3130 > was not found when attempting to remove it > Apr 25 12:48:29 xxxx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 3162 > was not found when attempting to remove it > > > They always come in triplets at the same second, and they are always (for me > and console-kit-daemon anyhow) indicate a real issue that was not there before > I started getting the errors. It's a warning that doesn't change the behaviour, and a bug in control-kit, report it against your distribution. > So whoever made the change to the code to start handling this error case may > have also changed some semantics that cause dependent applications to break. No, the "semantics" didn't change. It just throws a warning when you're using the function badly. > Thank you for giving more attention to this bug. I'm waiting for the information in comment 1. But it's not going to fix your ssh hanging. Ever. Because it's not related.
Hey Bastien, Thanks and apologies for making assumptions. I opened a new bug against consolekit on Ubuntu launchpad: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1313042
Closing this bug report as no further information has been provided. Please feel free to report this to https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ if you can provide the information that was asked for in a previous comment and if this still happens in a recent and supported version. Thanks!