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 433158 - crash in Deskbar: I don't know exactly why...
crash in Deskbar: I don't know exactly why...
Status: RESOLVED DUPLICATE of bug 424861
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-25 00:27 UTC by Wesley
Modified: 2007-04-25 02:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Wesley 2007-04-25 00:27:55 UTC 
What were you doing when the application crashed?
I don't know exactly why this is being reported as a crash.  My computer froze when opening a spreadsheet in Open Office.  This is the second time it has done that so I assume that was the action that cause the computer to lock up and possibly deskbar is interpreting that as a crash.  I also had firefox, a terminal, GkrellM, and Nautilus open.


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: Chaotic
Icon Theme: GnomeCorsair

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 ---------------------
alarm-notify.c:337 (alarm_msgport_replied) - 0x80c23b8: Replied to GUI thread
alarm-queue.c:560 (load_alarms_for_today) - From Tue Apr 24 19:25:18 2007
 to Tue Apr 24 19:25:18 2007
alarm-queue.c:497 (load_alarms) 
alarm-queue.c:526 (load_alarms) - Setting Call backs 
alarm-notify.c:349 (alarm_msg_received) - 0x80c61e8: Received at thread b5d9ab90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80c3f80
alarm-notifystarting 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
(gnome-panel:5831): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 25
--------------------------------------------------
Traceback (most recent call last):

+ Trace 130377

  • 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


Pedro Villavicencio





          2007-04-25 02:40:00 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 424861 ***