GNOME Bugzilla – Bug 550649
crash in Deskbar: Logged in and started th...
Last modified: 2008-09-03 13:24:08 UTC
What were you doing when the application crashed? Logged in and started the desktop Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.23.90 2008-08-18 (Ubuntu) BugBuddy Version: 2.23.91 System: Linux 2.6.27-2-generic #1 SMP Thu Aug 28 17:18:43 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10499906 Selinux: No Accessibility: Disabled GTK+ Theme: NewHuman Icon Theme: Neu Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- evolution-alarm-notify-Message: Thu Sep 4 03:00:00 2008 evolution-alarm-notify-Message: Wed Sep 3 14:16:13 2008 gnome-session[6178]: DEBUG(+): GsmXSMPClient: Set properties from client '0x1572de0 [evolution-alarm-notify 109e42589a2781beb2122044055713329300000061780024]' gnome-session[6178]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 0 gnome-session[6178]: DEBUG(+): GsmXSMPClient: Set properties from client '0x1572ba0 [nautilus 109e42589a2781beb2122044055640797000000061780003]' gnome-session[6178]: DEBUG(+): GsmXSMPClient: _GSM_Priority = 40 gnome-session[6178]: DEBUG(+): GsmXSMPClient: Set properties from client '0x1572ba0 [nautilus 109e42589a2781beb2122044055640797000000061780003]' gnome-session[6178]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 2 ** (nautilus:6379): WARNING **: Unable to add monitor: Not supported 36 (gnome-panel:6378): Gdk-WARNING **: /build/buildd/gtk+2.0-2.13.7/gdk/x11/gdkdrawable-x11.c:878 drawable is not a pixmap or window -------------------------------------------------- Traceback (most recent call last):
+ Trace 206247
gtk.gdk.threads_init()
*** Bug 550650 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version of pygtk. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 544946 ***