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 438911 - crash in Deskbar: Trying to go into standb...
crash in Deskbar: Trying to go into standb...
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)
: 438910 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-16 14:10 UTC by volton85
Modified: 2007-05-17 08:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description volton85 2007-05-16 14:10:46 UTC
What were you doing when the application crashed?
Trying to go into standby mode


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: Human

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/volton/Downloads/freemind/freemind/modes/mindmapmode/attributeactors (total watches = 76)
Watching directory /home/volton/Downloads/freemind/freemind/modes/mindmapmode/hooks (total watches = 77)
Watching directory /home/volton/Downloads/freemind/freemind/modes/mindmapmode/dialogs (total watches = 78)
Watching directory /home/volton/Downloads/freemind/freemind/modes/common/actions (total watches = 79)
Watching directory /home/volton/Downloads/freemind/freemind/modes/common/plugins (total watches = 80)
Watching directory /home/volton/Downloads/freemind/freemind/modes/common/listeners (total watches = 81)
Watching directory /home/volton/Downloads/freemind/freemind/modes/common/dialogs (total watches = 82)
Watching directory /home/volton/Downloads/freemind/accessories/plugins/util/xslt (total watches = 83)
Watching directory /home/volton/Downloads/freemind/accessories/plugins/util/html (total watches = 84)
Watching directory /home/volton/Downloads/freemind/accessories/plugins/util/window (total watches = 85)
Watching directory /home/volton/Downloads/freemind/freemind/modes/mindmapmode/actions/xml (total watches = 86)
starting indexing...
indexing #1 - /home/volton
flushing all words
Finished indexing. Waiting for new events...
--------------------------------------------------
Traceback (most recent call last):
  • 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 "/home/volton/.gnome2/deskbar-applet/handlers/deskbar-tracker-05.py", line 92 in __init__
    self.proxy_obj = self.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 Damien Durand 2007-05-16 16:55:29 UTC
*** Bug 438910 has been marked as a duplicate of this bug. ***
Comment 2 Susana 2007-05-17 08:44:43 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 ***