GNOME Bugzilla – Bug 446215
crash in Deskbar: Nothing
Last modified: 2007-06-12 03:52:52 UTC
What were you doing when the application crashed? Nothing Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 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 (114 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (gnome-system-monitor:24071): WARNING **: SELinux was found but is not enabled. checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last):
+ Trace 139931
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)
_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 419302 ***
(In reply to comment #0) > What were you doing when the application crashed? > Nothing > > > Distribution: Ubuntu 7.04 (feisty) > Gnome Release: 2.18.1 2007-04-10 (Ubuntu) > BugBuddy Version: 2.18.1 > > System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 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 (114 sec old) --------------------- > ** Message: GetValue variable 2 (2) > ** Message: GetValue variable 1 (1) > ** Message: GetValue variable 2 (2) > ** Message: GetValue variable 1 (1) > ** Message: GetValue variable 2 (2) > ** Message: GetValue variable 1 (1) > ** Message: GetValue variable 2 (2) > ** Message: GetValue variable 1 (1) > ** Message: GetValue variable 2 (2) > ** Message: GetValue variable 1 (1) > ** Message: GetValue variable 2 (2) > ** (gnome-system-monitor:24071): WARNING **: SELinux was found but is not > enabled. > checking for valid crashreport now > -------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 157, in > load_all > self.load (f) > File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 139, in > load > mod_instance = getattr (mod, handler) () > File "/usr/lib/deskbar-applet/handlers/tracker-handler.py", line 201, in > __init__ > self.tracker = > bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker') > File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 410, in > get_object > follow_name_owner_changes=follow_name_owner_changes) > File "/var/lib/python-support/python2.5/dbus/proxies.py", line 230, in > __init__ > _dbus_bindings.UInt32(0)) > File "/var/lib/python-support/python2.5/dbus/proxies.py", line 169, in > __call__ > reply_message = self._connection.send_message_with_reply_and_block(message, > timeout) > DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. > Possible causes include: the remote application did not send a reply, the > message bus security policy blocked the reply, the reply timeout expired, or > the network connection was broken. > So if this bug is resolved, why does it still happen to me? What do I need to do to fix it? Thanks!