Bug 453865 – 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 453865 - crash in Deskbar:


Summary:	crash in Deskbar:


Status:	RESOLVED DUPLICATE of bug 403752

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-07-05 05:25 UTC by mousavi.ehsan
Modified:	2007-07-05 08:02 UTC

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

Description mousavi.ehsan 2007-07-05 05:25:22 UTC

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

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) ---------------------
Watching directory /root/Documents/DIPC Reference/libs_files (total watches = 71)
Watching directory /root/InstallShield/Universal/common (total watches = 72)
Watching directory /root/Documents/DIPC Reference/61_files/ads_data (total watches = 73)
Watching directory /root/Documents/DIPC Reference/000059_files/ads_data (total watches = 74)
Watching directory /root/Documents/DIPC Reference/20-p0809_files/ads_data (total watches = 75)
Watching directory /root/InstallShield/Universal/common/Gen1 (total watches = 76)
Watching directory /root/InstallShield/Universal/common/Gen1/engine (total watches = 77)
Watching directory /root/InstallShield/Universal/common/Gen1/_vpddb (total watches = 78)
Watching directory /root/InstallShield/Universal/common/Gen1/engine/1.0 (total watches = 79)
Watching directory /root/InstallShield/Universal/common/Gen1/engine/1.0/library (total watches = 80)
Watching directory /root/InstallShield/Universal/common/Gen1/engine/1.0/ext (total watches = 81)
starting indexing...
indexing #1 - /root/Desktop/Download
flushing all words
Finished indexing. Waiting for new events...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 145827

File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 149 in load_all
```
self.load (f)
```
File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 131 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 "/usr/lib/python2.5/site-packages/dbus/bus.py", line 226 in get_object
```
follow_name_owner_changes=follow_name_owner_changes)
```
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 236 in __init__
```
self._named_service = conn.activate_name_owner(bus_name)
```
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 165 in activate_name_owner
```
self.start_service_by_name(bus_name)
```
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 261 in start_service_by_name
```
'su', (bus_name, flags)))
```
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 598 in call_blocking
```
message, timeout)
```

DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/trackerd exited with status 0

Comment 1 Ghislain MARY 2007-07-05 08:02:33 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 ***