Bug 409696 – crash in Deskbar: Login

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 409696 - crash in Deskbar: Login


Summary:	crash in Deskbar: Login


Status:	RESOLVED DUPLICATE of bug 408994

Product:	deskbar-applet
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Deskbar Applet Maintainer(s)
QA Contact:	Deskbar Applet Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-19 18:39 UTC by Jonas Bonn
Modified:	2007-02-19 21:30 UTC

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

Description Jonas Bonn 2007-02-19 18:39:35 UTC

What were you doing when the application crashed?
Login


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.17.91 2007-02-12 (Ubuntu)
BugBuddy Version: 2.17.3

System: Linux 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

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-queue.c:2008 (alarm_queue_add_async) - 0x6b1da0
alarm-queue.c:560 (load_alarms_for_today) - From Mon Feb 19 19:44:23 2007
 to Mon Feb 19 19:44:23 2007
alarm-queue.c:497 (load_alarms) 
alarm-queue.c:526 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x6ddbf0: Replied to GUI thread
alarm-notify.c:349 (alarm_msg_received) - 0x6e4910: Received at thread 42044940
alarm-queue.c:2008 (alarm_queue_add_async) - 0x6b3ea0
alarm-queue.c:560 (load_alarms_for_today) - From Mon Feb 19 19:44:23 2007
 to Mon Feb 19 19:4Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 112052

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 412 in get_object
```
follow_name_owner_changes=follow_name_owner_changes)
```
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 232 in __init__
```
_dbus_bindings.UInt32(0))
```
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 171 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-02-19 21:30:42 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 408994 ***