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 415892 - crash in Deskbar: Just logged in. Tracker ...
crash in Deskbar: Just logged in. Tracker ...
Status: RESOLVED DUPLICATE of bug 414067
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
: 421415 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-08 00:34 UTC by guido.conaldi
Modified: 2007-03-22 17:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description guido.conaldi 2007-03-08 00:34:19 UTC 
What were you doing when the application crashed?
Just logged in. Tracker search plugins were enabled.


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.17.92 2007-02-27 (Ubuntu)
BugBuddy Version: 2.17.4

System: Linux 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaGilouche
Icon Theme: Tango

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 ---------------------
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/fipm/.evolution/memos/local/system 
alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/fipm/.evolution/memos/local/system - Calendar Open Async... 0x80dcea0
alarm-notify.c:393 (cal_opened_cb) file:///home/fipm/.evolution/calendar/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80d9b18: Received at thread b65a0b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80bd290
alarm-queue.c:560 (load_alarms_for_today) - From Thu Mar  8 01:32:53 2007
 to Thu Mar  8 01:32:53 2007
alarm-queue.c:497 (load_alarms) 
alarm-notify.c:393 (cal_opened_cb) file:///home/fipm/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:393 (cal_opened_cb) file:///home/fipm/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-queue.c:526 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80d9b18
--------------------------------------------------
Traceback (most recent call last):

+ Trace 116750

  • 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.Spawn.ChildExited: Process /usr/bin/trackerd exited with status 0 






Comment 1


Damien Durand





          2007-03-08 17:53:49 UTC
        



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






Comment 2


Damien Durand





          2007-03-22 17:03:53 UTC
        



*** Bug 421415 has been marked as a duplicate of this bug. ***