GNOME Bugzilla – Bug 449825
crash in Deskbar: Starting GNOME as usual.
Last modified: 2007-06-23 22:13:41 UTC
What were you doing when the application crashed? Starting GNOME as usual. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.4 2007-06-18 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 --------------------- Adding plugin text (Text) Adding plugin scale (Měřítko) Adding plugin screenshot (Screenshot) Adding plugin animation (Animations) Adding plugin minimize (Efekt minimalizace) Adding plugin svg (Svg) Adding plugin wall (Desktop Wall) Adding plugin switcher (Přepínač aplikací) Adding plugin neg (Negative) Adding plugin fs (Userspace File System) Adding core settings (General Options) Adding plugin blur (Blur Windows) Adding plugin move (Přesunout okno) Add ***MEMORY-WARNING***: [11534]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is li -------------------------------------------------- Traceback (most recent call last):
+ Trace 142703
self.load (f)
mod_instance = getattr (mod, handler) ()
self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
follow_name_owner_changes=follow_name_owner_changes)
self._named_service = conn.activate_name_owner(bus_name)
self.start_service_by_name(bus_name)
'su', (bus_name, flags)))
message, timeout)
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 403752 ***