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 439306 - crash in Deskbar: closing session
crash in Deskbar: closing session
Status: RESOLVED DUPLICATE of bug 389984
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-05-17 21:46 UTC by manza
Modified: 2007-05-18 01:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description manza 2007-05-17 21:46:53 UTC
What were you doing when the application crashed?
closing session


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-05-16 (Gentoo)
BugBuddy Version: 2.16.0

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

Traceback (most recent call last):
  • File "/usr/lib/python2.4/site-packages/deskbar/ModuleLoader.py", line 157 in load_all
    self.load (f)
  • File "/usr/lib/python2.4/site-packages/deskbar/ModuleLoader.py", line 139 in load
    mod_instance = getattr (mod, handler) ()
  • File "/usr/lib/deskbar-applet/handlers/tracker-handler.py", line 202 in __init__
    bus = dbus.SessionBus()
  • File "//usr/lib/python2.4/site-packages/dbus/_dbus.py", line 669 in __new__
    mainloop=mainloop)
  • File "//usr/lib/python2.4/site-packages/dbus/_dbus.py", line 293 in __new__
    mainloop=mainloop)
DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-cVf02BS5BJ: Connessione rifiutata

Comment 1 Pedro Villavicencio 2007-05-18 01:59:17 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 389984 ***