GNOME Bugzilla – Bug 402090
crash in Deskbar: I have just opened my se...
Last modified: 2007-02-05 23:20:51 UTC
What were you doing when the application crashed? I have just opened my session Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.90 2007-01-23 (Ubuntu) BugBuddy Version: 2.17.3 System: Linux 2.6.20-5-powerpc64-smp #2 SMP Sat Jan 6 10:08:33 UTC 2007 ppc64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 260767604 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 260767604 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 -------------------------------------------------- Traceback (most recent call last):
+ Trace 106275
self.load (f)
mod_instance = getattr (mod, handler) ()
self.proxy_obj = self.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)
After looking at the error it is pretty minor: I carried a tracker handler with my $HOME while tracker is not installed here. A more graceful fail in such case would be great... To get it working again, I removed this handler. Then I had to kill deskbar (_without reloading it_) and then add it again to my panel (I guess that a disconnect/reconnect would have worked as well).
*** Bug 402444 has been marked as a duplicate of this bug. ***
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 403752 ***