GNOME Bugzilla – Bug 515397
crash in Deskbar: gebootet
Last modified: 2008-02-10 10:33:38 UTC
What were you doing when the application crashed? gebootet Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-07-30 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (13 sec old) --------------------- alarm-notify.c:393 (cal_opened_cb) file:///home/freihaut/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2008 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80da208: Received at thread b4585b90 alarm-queue.c:1959 (alarm_queue_add_async) - 0x80d7b40 alarm-queue.c:542 (load_alarms_for_today) - From Sat Feb 9 13:20:12 2008 to Sat Feb 9 13:20:12 2008 alarm-queue.c:479 (load_alarms) alarm-queue.c:508 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80da208: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2008 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarmERROR: tracker_dbus_init() could not get the session bus process 5174: arguments to dbus_connection_register_object_path() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5280. This is normally a bug in some application using the D-Bus library. -------------------------------------------------- Traceback (most recent call last):
+ Trace 188647
self.load (f)
mod_instance = getattr (mod, handler) ()
bus = dbus.SessionBus()
mainloop=mainloop)
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 366899 ***