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 450467 - crash in Deskbar: Nada
crash in Deskbar: Nada
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-06-23 21:30 UTC by marco.sieben
Modified: 2007-06-23 22:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description marco.sieben 2007-06-23 21:30:31 UTC 
What were you doing when the application crashed?
Nada


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3167.fc7 #1 SMP Thu May 17 23:05:53 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks_Cairo-Olive2
Icon Theme: Cherry-Soda

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 (43 sec old) ---------------------
Initializing nautilus-search-tool extension
seahorse nautilus module initialized
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:53: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:54: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:53: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:54: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
Bucket count (max is 524288) is 294908 and Record Count is 266726
preferred bucket count is 266726
starting database closure for thread main
Database closed for thread main
starting 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 143215

  • 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 "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 410 in get_object 
    follow_name_owner_changes=follow_name_owner_changes)
  • File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230 in __init__ 
    _dbus_bindings.UInt32(0))
  • File "/usr/lib/python2.5/site-packages/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


Pedro Villavicencio





          2007-06-23 22:01:01 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 ***