GNOME Bugzilla – Bug 430468
crash in Deskbar: during login
Last modified: 2007-04-16 23:26:19 UTC
What were you doing when the application crashed? during login Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 --------------------- however, pixmaps only have colormap by default if they were created with a non-NULL window argument. Otherwise a colormap must be set on them with gdk_drawable_set_colormap (gtk-window-decorator:5964): Gdk-WARNING **: Using Cairo rendering requires the drawable argument to have a specified colormap. All windows have a colormap, however, pixmaps only have colormap by default if they were created with a non-NULL window argument. Otherwise a colormap must be set on them with gdk_drawable_set_colormap (gnome-panel:5944): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 24 Impossibile aprire il file .desktop «file:///home/paolo/Desktop/supershow.desktop» per l'icona di avvio: Nessun file o directory Impossibile aprire il file .desktop «file:///home/paolo/Desktop/D4X.desktop» per l'icona di avvio: Nessun file o directory Impossibile aprire il file .desktop «/usr/share/applications/control-center.desktop» per l'icona di avvio: Nessun file o directory checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last):
+ Trace 128356
self.load (f)
mod_instance = getattr (mod, handler) ()
obj = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
follow_name_owner_changes=follow_name_owner_changes)
_dbus_bindings.UInt32(0))
reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 430467 ***