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 512448 - crash in Deskbar: did not know it crashed
crash in Deskbar: did not know it crashed
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: 2008-01-27 20:47 UTC by ewomer
Modified: 2008-01-27 21:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description ewomer 2008-01-27 20:47:47 UTC
What were you doing when the application crashed?
did not know it crashed


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.5 2008-01-15 (Ubuntu)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-custom #1 SMP PREEMPT Sat Jan 26 16:41:10 EST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
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 ---------------------
** (gnome-screensaver:6545): WARNING **: failed to register with the message bus
Window manager warning: Failed to read saved session file /home/eric/.metacity/sessions/default0.ms: Failed to open file '/home/eric/.metacity/sessions/default0.ms': No such file or directory
libnotify-Message: Unable to get session bus: Failed to connect to socket /tmp/dbus-PA0PNu744E: Connection refused
** (tracker-applet:6569): WARNING **: failed: notify_init()
libnotify-Message: Unable to get session bus: Failed to connect to socket /tmp/dbus-PA0PNu744E: Connection refused
DBUS ERROR: org.freedesktop.DBus.Error.NoServer occurred with message Failed to connect to socket /tmp/dbus-PA0PNu744E: Connection refused
ERROR: could not get the dbus session bus - exiting
libnotify-Message: Unable to get session bus: Failed to connect to socket /tmp/dbus-PA0PNu744E: Connection refused
system-config-printer-applet: unable to initialize pynotify
system-config-printer-applet: failed to connect to session D-Bus
  PID TTY          TIME CMD
 6510 ?        00:00:00 pulseaudio
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ModuleLoader.py", line 164 in load_all
    self.load (f)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ModuleLoader.py", line 142 in load
    modules = self.import_module (filename)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ModuleLoader.py", line 128 in import_module
    if not getattr(module, "has_requirements" )():
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/tomboy.py", line 170 in has_requirements
    return tomboy_installed() and tomboy_correct_version()
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/tomboy.py", line 186 in tomboy_installed
    bus = dbus.SessionBus()
  • File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 217 in __new__
    mainloop=mainloop)
  • File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 106 in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  • File "/var/lib/python-support/python2.5/dbus/bus.py", line 125 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-PA0PNu744E: Connection refused

Comment 1 Gianluca Borello 2008-01-27 21:06:23 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 ***