GNOME Bugzilla – Bug 550439
crash in Deskbar:
Last modified: 2008-09-02 16:19:18 UTC
What were you doing when the application crashed? 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:20:02 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499906 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 --------------------- x-session-manager[7634]: DEBUG(+): GsmXSMPClient: Client '0x9902d48 [evolution-exchange-storage 10679344b5ad09fee4122035634030812100000076340030]' received SaveYourselfDone(success = True) x-session-manager[7634]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x9938970, FALSE, 3, 9, 32771, 0) Got Event! 33, -1 x-session-manager[7634]: DEBUG(+): GsmXSMPClient: Set properties from client '0x9902f78 [evolution-alarm-notify 10679344b5ad09fee4122035633332183600000076340015]' x-session-manager[7634]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 0 Got Event! 33, -1 Unable to open desktop file /home/mychell/Desktop/gksu.desktop for panel launcher: No such file or directory (gnome-panel:7725): Gdk-WARNING **: /build/buildd/gtk+2.0-2.13.7/gdk/x11/gdkdrawable-x11.c:878 drawable is not a pixmap or window Got Event! 33, -1 Cannot index Thunderbird contacts because a System.ArgumentNullException was thrown: Argument cannot be null. Parameter name: path Cannot index Thunderbird contacts because a System.ArgumentNullException was thrown: Argument cannot be null. Parameter name: path 36 -------------------------------------------------- Traceback (most recent call last):
+ Trace 206141
gtk.gdk.threads_init()
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. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 544946 ***