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 415573 - crash in Deskbar: I just logged in. The st...
crash in Deskbar: I just logged in. The st...
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-03-07 03:27 UTC by hieu.d.hoang
Modified: 2007-03-07 11:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description hieu.d.hoang 2007-03-07 03:27:30 UTC
What were you doing when the application crashed?
I just logged in.
The start up programs are Beryl and gnome-terminal (i put those in a bash script and start it in gnome-session-properties), and the normal stuffs minus network manager.
I tried disable Tracker from gnome-session start up progs, this same bug report still comes up.


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.17.92 2007-02-27 (Ubuntu)
BugBuddy Version: 2.17.4

System: Linux 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Blubuntu
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 ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'.
Window manager warning: "" found in configuration database is not a valid value for keybinding "toggle_shaded"
/usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
/usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
libberylsettings: Couldn't get vtable from '/usr/lib/beryl/libgroup.so' plugin
libberylsettings: Couldn't get vtable from '/usr/lib/beryl/libshowdesktop.so' plugin
libberylsettings: Couldn't get vtable from '/usr/lib/beryl/libsnow.so' plugin
libberylsettings: Couldn't get vtable from '/usr/lib/beryl/libzoom.so' plugin
libberylsettings: Couldn't get vtable from '/usr/lib/beryl/libtext.so' plugin
libberylsettings: Couldn't get vtable from '/usr/lib/beryl/libtile.so' plugin
libberylsettings: Couldn't get vtable from '/usr/lib/beryl/libplane.so' plugin
--------------------------------------------------
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/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 Susana 2007-03-07 11:52:40 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 403752 ***