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 437293 - crash in Deskbar:
crash in Deskbar:
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-09 21:26 UTC by Javier Cabezas
Modified: 2007-05-09 22:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Javier Cabezas 2007-05-09 21:26:27 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.18.1 2007-04-11 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
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 ---------------------
Watching directory /home/javi/Desktop/Lapiz/Doc/Phrack/phrack09 (total watches = 490)
Watching directory /home/javi/Desktop/Lapiz/Doc/Phrack/phrack08 (total watches = 491)
Watching directory /home/javi/Desktop/Lapiz/Doc/Phrack/phrack07 (total watches = 492)
Watching directory /home/javi/Desktop/Lapiz/Doc/Phrack/phrack01 (total watches = 493)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documento/Presentaciones (total watches = 494)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documento/Memoria (total watches = 495)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documento/Informe (total watches = 496)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documento/Papers (total watches = 497)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documentación/Arquitectura (total watches = 498)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documentación/Dynamic Linking (total watches = 499)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documentación/Diablo (total watches = 500)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documentación/Code rewriting (total watches = 501)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documentación/ELF (total watches = 502)
Watching directory /home/javi/Desktop/Lapiz/PFC/Documentación/L4 (total watches = 503)
Watching directory /home/javi/Desktop/Lapiz/PFC/Work/L4Diablo (total watches = 504)
--------------------------------------------------
Traceback (most recent call last):

+ Trace 133360

  • 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-09 22:10:00 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 for tracker.


*** This bug has been marked as a duplicate of 403752 ***