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 434611 - crash in Deskbar: I'm using beryl as windo...
crash in Deskbar: I'm using beryl as windo...
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-04-30 14:48 UTC by satkata
Modified: 2007-04-30 17:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description satkata 2007-04-30 14:48:16 UTC 
What were you doing when the application crashed?
I'm using beryl as window-manager and since I have changed my theme to Neutronium-GTK2, every time I log into the deskbar is crashing. manually loading after the crash report comes up is no problem and everything is ok.
It could be some problem of the theme, but I don't know.


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: Neutronium-Gtk2
Icon Theme: OsX_MoD

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) ---------------------
alarm-queue.c:497 (load_alarms) 
alarm-queue.c:526 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80cc0a8: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_receseahorse nautilus module initialized
Unable to open desktop file file:///home/satkata/Desktop/gnome-system-monitor.desktop for panel launcher: No such file or directory
Bucket count (max is 524288) is 524284 and Record Count is 514681
preferred bucket count is 514681
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 131460

  • 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-04-30 17:24:30 UTC
        



It's related to the tracker plugin. I believe it was actually the tracker daemon itself, but the bug I'm marking this a duplicate of has the details.

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 ***