GNOME Bugzilla – Bug 454182
crash in Deskbar: I installed the deskbar-...
Last modified: 2007-07-07 21:18:49 UTC
What were you doing when the application crashed? I installed the deskbar-applet with libdeskbar-tracker. So, I restarted the pc and the applet crashed. It always crashes on each restart. Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaCandy Icon Theme: nuoveXT-1.6 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 --------------------- starting database closure for thread main Database closed for thread main starting database closure for thread main Database closed for thread main Checking tracker DB version...Current version is 15 and needed version is 13 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (gnome-panel:4040): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 25 Conky: desktop window (e0005e) is subwindow of root window (1a5) Conky: window type - override Conky: drawing to created window (2c00002) Conky: drawing to double buffer -------------------------------------------------- Traceback (most recent call last):
+ Trace 146056
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)))
reply_message = self.send_message_with_reply_and_block(
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 ***