GNOME Bugzilla – Bug 550308
crash in Deskbar: Logging on (and I didn't...
Last modified: 2008-09-02 09:22:28 UTC
What were you doing when the application crashed? Logging on (and I didn't really notice a crash) 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: NewHuman Icon Theme: Human 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 (10 sec old) --------------------- evolution-alarm-notify-Message: Mon Sep 1 23:18:42 2008 x-session-manager[12786]: DEBUG(+): GsmXSMPClient: Set properties from client '0x811f4f0 [gnome-panel 10dc60921b8f758a1e12203039111290700000127860002]' (gnome-panel:12947): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x818b958 (gnome-panel:12947): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x818b958 [1;38mwarning : [0m [0;37m(cairo-dock-surface-factory.c:cairo_dock_create_surface_from_image:352) [0m Attention : Failed to open file '/home/excogitation/Pictures/System/Icons/icon_lock_256': No such file or directory Initializing nautilus-share extension ** (nautilus:12948): WARNING **: Unable to add monitor: Not supported (gnome-panel:12947): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 30 -------------------------------------------------- Traceback (most recent call last):
+ Trace 206036
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 ***