Bug 449805 – crash in Deskbar:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 449805 - crash in Deskbar:


Summary:	crash in Deskbar:


Status:	RESOLVED DUPLICATE of bug 434229

Product:	tracker
Classification:	Core
Component:	General
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Jamie McCracken
QA Contact:	Jamie McCracken

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-21 15:21 UTC by gregkise
Modified:	2007-06-23 22:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description gregkise 2007-06-21 15:21:11 UTC

What were you doing when the application crashed?



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: Clearlooks
Icon Theme: gnome

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 (6 sec old) ---------------------
alarm-notify.c:337 (alarm_msgport_replied) - 0x80d4f60: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) file:///home/greg/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80cf680: Received** Message: <information>	You are now connected to the wireless network 'monkeyshine'.
Traceback (most recent call last):

+ Trace 142689

File "/home/greg/.nautilus/python-extensions/tracker-tags-tab.py", line 13 in __init__
```
'/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)
```

dbus.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

--------------------------------------------------
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.

Comment 1 Pedro Villavicencio 2007-06-23 22:15:20 UTC

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 434229 ***