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 490360 - crash in Deskbar: starting the computer
crash in Deskbar: starting the computer
Status: RESOLVED DUPLICATE of bug 366899
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-10-26 02:46 UTC by Brian Haley
Modified: 2007-10-26 16:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Brian Haley 2007-10-26 02:46:43 UTC 
What were you doing when the application crashed?
starting the computer


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.0 2007-09-17 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 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 (30 sec old) ---------------------
alarm-notify.c:349 (alarm_msg_received) - 0x80d21e0: Received at thread b6624b90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80b0190
alarm-notify.c:393 (cal_opened_cb) file:///home/brian/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-queue.c:581 (load_alarms_for_today) - From Thu Oct 25 19:45:44 2007
 to Thu Oct 25 19:45:44 2007
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:349 (alarm_msg_received) -ERROR: tracker_dbus_init() could not get the session bus
DBUS ERROR: org.freedesktop.DBus.Error.NoServer occurred with message Failed to connect to socket /tmp/dbus-p2BmirRHgM: Connection refused
process 5406: 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.
(gnome-panel:5381): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -10 and height 25
--------------------------------------------------
Traceback (most recent call last):

+ Trace 172922

  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarApplet.py", line 108 in <lambda> 
    ("Prefs", lambda a,b: self.__controller.on_show_preferences(a)),
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/CuemiacWindowController.py", line 47 in on_show_preferences 
    prefs = DeskbarPreferences(self._model)
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/preferences/DeskbarPreferences.py", line 57 in __init__ 
    self.__enable_newstuffmanager( self.__is_nsm_available() )
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/preferences/DeskbarPreferences.py", line 137 in __is_nsm_available 
    bus = dbus.SessionBus()
  • File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 218 in __new__ 
    mainloop=mainloop)
  • File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 107 in __new__ 
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  • File "/var/lib/python-support/python2.5/dbus/bus.py", line 121 in __new__ 
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-p2BmirRHgM: Connection refused 






Comment 1


Sebastian Pölsterl





          2007-10-26 16:33:32 UTC
        



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