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 427916 - crash in Deskbar: Deskbar crashed at the s...
crash in Deskbar: Deskbar crashed at the s...
Status: RESOLVED DUPLICATE of bug 422566
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-04-09 16:35 UTC by denk900
Modified: 2007-04-09 22:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description denk900 2007-04-09 16:35:19 UTC
What were you doing when the application crashed?
Deskbar crashed at the startup. I don't know if this will help you, but I've a problem with "Gnome settings daemon"; Gnome takes a long time (~3 min) to load and finally i get this error: "[...]Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.[...]"
I'm using Ubuntu Feisty (beta). I have the error with g-s-d since i tried (unsuccesfully) to upgrade gnome from 2.16 to 2.18 (I was using Ubuntu edgy). Then I installed Feisty hoping this could resolve the problem, but nothing changed...The deskbar started crashing after the upgrade...not every time...I use Compiz and Avant Windows Navigator too.
Hope this'll help you!



Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.0 2007-03-13 (Ubuntu)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
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 (10 sec old) ---------------------
** (gnome-session:6846): WARNING **: Host name lookup failure on localhost.
Bonobo accessibility support initialized
Bonobo accessibility support initialized
Bonobo accessibility support initialized
compiz.real: water: GL_ARB_fragment_program is missing
(compiz-tray-icon:6962): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(compiz-tray-icon:6962): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(compiz-tray-icon:6962): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(compiz-tray-icon:6962): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
GTK Accessibility Module initialized
--------------------------------------------------
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 "/usr/lib/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-04-09 22:25:34 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 422566 ***