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 435133 - crash in Deskbar: The Gnome session was st...
crash in Deskbar: The Gnome session was st...
Status: RESOLVED DUPLICATE of bug 403752
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-05-02 10:17 UTC by michamos
Modified: 2007-05-02 16:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description michamos 2007-05-02 10:17:00 UTC 
What were you doing when the application crashed?
The Gnome session was starting


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Tangerine

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 (13 sec old) ---------------------
alarm-notify.c:393 (cal_opened_cb) file:///home/mic/.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) - 0x80bcdd0: Replied to GUI thread
alarm-notify.c:349 (alarm_msg_received) - 0x80bcdf0: Received at thread b55beb90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80db240
alarm-queue.c:560 (load_alarms_for_today) - From Wed May  2 12:16:03 2007
 to Wed May  2 12:16:03 2007
alarm-queue.c:497 (load_alarms) 
alarm-queue.c:526 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80bcdf0: Replied to GUI thread
alarm-notify.c:349 (alarm_msg_received) - 0x80df638: Received at threastarting database closure for thread main
Database closed for thread main
Checking tracker DB version...Current version is 15 and needed version is 13
--------------------------------------------------
Traceback (most recent call last):

+ Trace 131851

  • 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


Mart Raudsepp





          2007-05-02 16:26:38 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 403752 ***