Description of problem: Gnome session starts without most "startup applets" in upper right part of the panel (e.g., sound applet, network applet, etc.). I see this in ~/.xsession-errors: (gnome-settings-daemon:1782): GLib-GObject-CRITICAL **: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed (gnome-settings-daemon:1782): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed and this (similar) in /var/log/messages: Jul 8 06:16:09 tlondon kernel: dp_aux_ch timeout status 0x51450085 Jul 8 06:16:09 tlondon kernel: dp_aux_ch timeout status 0x51450085 Jul 8 06:16:11 tlondon gdm-simple-greeter[1460]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed Jul 8 06:16:11 tlondon gdm-simple-greeter[1460]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed Jul 8 06:16:14 tlondon auditd[1571]: Started dispatcher: /sbin/audispd pid: 1573 Jul 8 06:16:14 tlondon audispd: af_unix plugin initialized Jul 8 06:16:14 tlondon audispd: audispd initialized with q_depth=80 and 2 active plugins Jul 8 06:16:14 tlondon auditd[1571]: Init complete, auditd 1.7.13 listening for events (startup state enable) Version-Release number of selected component (if applicable): gnome-settings-daemon-2.27.3-2.fc12.x86_64 gdm-2.26.1-13.fc12.x86_64 How reproducible: Happened several times yesterday and this morning. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Happened again on very next boot/login. Here is complete ~/.xsession-errors: [tbl@tlondon ~]$ cat .xsession-errors imsettings information ========================== Is DBus enabled: yes Is imsettings enabled: yes Is GTK+ supported: yes Is Qt supported: no DESKTOP_SESSION: gnome DISABLE_IMSETTINGS: IMSETTINGS_DISABLE_DESKTOP_CHECK: DBUS_SESSION_BUS_ADDRESS: unix:abstract=/tmp/dbus-fDxF6SbASR,guid=bc5da65b0772eb40b4c6773b4a54a356 GTK_IM_MODULE: QT_IM_MODULE: xim XMODIFIERS: @im=none IMSETTINGS_MODULE: none IMSETTINGS_INTEGRATE_DESKTOP: yes GNOME_KEYRING_SOCKET=/tmp/keyring-ngTQ4a/socket SSH_AUTH_SOCK=/tmp/keyring-ngTQ4a/socket.ssh Initializing nautilus-gdu extension compiz (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format (gnome-settings-daemon:1761): GLib-GObject-CRITICAL **: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed (gnome-settings-daemon:1761): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed ** (nm-applet:1799): WARNING **: Failed to show notification: Message did not receive a reply (timeout by message bus) ** (gnome-screensaver:1998): WARNING **: screensaver already running in this session [tbl@tlondon ~]$ Hmmm... I tried to run "gimp" to crop a screenshot of the entire screen, but it won't start: [tbl@tlondon ~]$ gimp (gimp:2279): GLib-GObject-WARNING **: specified class size for type `GimpOperationPointFilter' is smaller than the parent type's `GeglOperationPointFilter' class size (gimp:2279): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gimp:2279): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed (gimp:2279): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gimp:2279): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `<invalid>' <<<< HANGS HERE >>>> This related?
Those warnings are unrelated. The problem you are seeing is a redraw issue in GTK+.
I'm not seeing this today with gtk2-devel-docs-2.17.3-2.fc12.x86_64 gtk2-devel-2.17.3-2.fc12.x86_64 gtk2-debuginfo-2.17.3-2.fc12.x86_64 gtk2-engines-2.18.1-1.fc11.x86_64 gtk2-2.17.3-2.fc12.x86_64 Fixed? Random?
Random. It has not been fixed yet, unfortunately.
Yeah, still happens sometimes with gtk2-2.17.3-2.fc12.x86_64. Let me know if there is some debugging/testing I can do....
*** Bug 511010 has been marked as a duplicate of this bug. ***
As of 2.17.3 I'm seeing one application failing to redraw/refresh text boxes - but if you just pass the mouse over each affected line, it refreshes that line. Same redraw issue?
Gimp not starting is bug #510209.
*** Bug 513108 has been marked as a duplicate of this bug. ***
*** Bug 515302 has been marked as a duplicate of this bug. ***
Created attachment 356413 [details] yum.log after fix The notification icons are visible now, although gtk2 was not updated. Attaching a complete yum.log just in case. As far as my bug 513108 is concerned, the issue is fixed.
Created attachment 356515 [details] Screenshot of notification area showing missing applets/icons I'm still (randomly?) seeing this problem. Icons appear on some logins; are missing on other logins. In this case, "gnome-volume-control-applet" is missing, but the process is running: [tbl@tlondon ~]$ ps agx | grep volume 1661 ? S 0:00 gnome-volume-control-applet 1699 ? S 0:00 /usr/libexec/gvfs-gdu-volume-monitor 1707 ? S 0:00 /usr/libexec/gvfs-gphoto2-volume-monitor 2910 pts/1 S+ 0:00 grep volume [tbl@tlondon ~]$ The volume applet is not just "there but invisible"; clicking on the empty space does not connect to it.... also missing are NetworkManager, battery/power, ... I think I get the "proper" display/use of the applets/icons about 1 in 3 logins.
For the record, currently running: gtk2-engines-2.18.2-4.fc12.x86_64 gtk2-debuginfo-2.17.6-4.fc12.x86_64 gtk2-2.17.6-4.fc12.x86_64 gtk2-devel-2.17.6-4.fc12.x86_64 gtk2-devel-docs-2.17.6-4.fc12.x86_64
Thanks, but there i no need to provide detailed version updates here. The bug is known, it is known to not be fixed, and it will be tackled when the relevant developer is back from vacation next week.
*** Bug 516544 has been marked as a duplicate of this bug. ***
This is claimed to be fixed in gtk2-2.17.7-1.fc12, which has been tagged in for the Alpha release. I have just checked and it appears fixed here, and is confirmed fixed by Jesse Keating and Warren Togami on the tag request. Closing bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
actually, mclasen says it can still happen but is less easy to hit. Don't know the technical details, but I defer to him, re-opening. Impact should be mitigated for Alpha, though, by the looks of things. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Was seeing issues with 2.17.6-6, which had a changelog that claimed it was fixed. Still seeing 100% consistent failures in my one GTK2 app (gyachi) with 2.17.7-1. Is my 100% issue a different one than this "can still happen", or am I the proud owner of a smoketest app? Am willing to do low-level debugging if somebody has a hint of what to go look at....
I'm seeing all the icons back in the notification area without having to randomly kill it off so that's definitely an improvement but I can't see the running applications in the bottom panel. I'm not sure if that's the same issue though.
This seems all sorts of confused; I didn't claim that this bug was fixed in 2.17.6-6. That update fixed root window drawing problems in gdm and elsewhere. 2.17.7 makes the problem in this bug (missing status icons) much less frequent. I know nothing about problems with the taskbar in the bottom panel, and that is entirely unrelated to what this bug is about...
(In reply to comment #20) > This seems all sorts of confused; I didn't claim that this bug was fixed in > 2.17.6-6. That update fixed root window drawing problems in gdm and elsewhere. > 2.17.7 makes the problem in this bug (missing status icons) much less frequent. > I know nothing about problems with the taskbar in the bottom panel, and that is > entirely unrelated to what this bug is about... I was seeing the missing status icons. That is fixed with the 2.17.7 release for me on a eeePC 901 netbook. I was wondering whether the missing apps in the taskbar might be related as the issue started the same time AFAICR. I asked if it was possibly related due to the "much less frequent" part of the fix report. If its not that's fine, I'll look for or report another bug, not much point if its the same.
Could be that you simply lost the taskbar applet from your panel config somehow ?
The notification applet on an Acer Aspire 5315 is just a big grey block even with the latest GTK2. In the past I only had to remove and add the Applet about 3 times to get it to appear, now its around 10 times ! My display hardware is Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03), using the Intel device driver
(In reply to comment #22) > Could be that you simply lost the taskbar applet from your panel config somehow Yes, it appears you are right, and I didn't even know you could remove that bit! Sorry for the fuzz!
stephen: when you say 'the latest', can you be precise? you need gtk2-2.17.7-1.fc12 or higher, please give your 'rpm -q gtk2' output. you also need to restart X after installing the update. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Sorry - I read this in the changelog: * Fri Aug 07 2009 Matthias Clasen <mclasen> - 2.17.6-5 - Fix gdm background drawing and misinterpreted it as being a fix for the redisplay issue.
Adam, the output from rpm -q gtk2 is : gtk2-2.17.7-1.fc12.x86_64 gtk2-2.17.7-1.fc12.i686 Additional information is that when I rebooted yesterday the notification area came up cleanly first time, when I rebooted today I had to remove it and add it again to get it displayed and as I say sometimes I have to add it 9 or 10 times to get it displayed. This is since I got 2.17.7-1
stephen: that's the right version...i'm assuming you have both 32-bit and 64-bit versions installed as you have a need to run some GTK+-based software in 32-bit mode? But thanks for the confirmation. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 526670 has been marked as a duplicate of this bug. ***
Fixed in gtk2-2.18.2-1.fc12
Works here. Thanks!
Hmm, I'm seeing this intermittently with gtk2-2.18.9-3.fc12.x86_64; for example, when I just started XChat, the Seahorse icon took the XChat icon's place (and would not respond). Sometimes the correct icon is drawn in after a while, but not always.