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 432006 - crash in Deskbar: First boot after upgradi...
crash in Deskbar: First boot after upgradi...
Status: RESOLVED DUPLICATE of bug 421415
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-21 15:18 UTC by thegynius
Modified: 2007-04-21 15:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description thegynius 2007-04-21 15:18:21 UTC 
What were you doing when the application crashed?
First boot after upgrading Ubuntu 6.10 Edgy Eft to 7.04 Feisty Fawn.
Starting my user's gnome session automatically gdesklets starts.
This crashes gnome-panel and the whole gnome session.
I just uninstalled gDesklets from a text terminal:
# sudo apt-get remove gdesklets
After a system restart the gnome session works properly.


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: Vignette
Icon Theme: Kreski-Lines

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 (14 sec old) ---------------------
alarm-notify.c:368 (alarm_notify_new) - Alarm Notify New 
 alarm-notify.c:304 (alarm_channel_setup) - Channel Setup
 alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify
alarm-queue.c:1875 (alarm_queue_init)
alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Sun Apr 22 00:00:00 2007
 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/gyo/.evolution/tasks/local/system 
alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/gyo/.evolution/tasks/local/system - Calendar Open Async... 0x80bd9a0
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/gyo/.evolution/memos/local/system 
alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/gyo/.evolution/memos/local/system - Calendar Open Async... 0x80d7f10
alarm-notify.c:393 (cal_opened_cb) file:///home/gyo/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80dd930: Received at thread b55c1b90
alarm-queue.c:20
(gnome-panel:6250): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 24
--------------------------------------------------
Traceback (most recent call last):

+ Trace 129537

  • 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


Damien Durand





          2007-04-21 15:56:39 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 421415 ***