Bug 489839 – crash in Deskbar: Startet nicht

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 489839 - crash in Deskbar: Startet nicht


Summary:	crash in Deskbar: Startet nicht


Status:	RESOLVED DUPLICATE of bug 366899

Product:	deskbar-applet
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Deskbar Applet Maintainer(s)
QA Contact:	Deskbar Applet Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-24 15:40 UTC by kai
Modified:	2007-10-24 17:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description kai 2007-10-24 15:40:44 UTC

What were you doing when the application crashed?
Startet nicht


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Samui-2.0
Icon Theme: glass-icons

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 (23 sec old) ---------------------
  "priv", self.configTree.properties, None, -1)
/var/lib/python-support/python2.5/driconf_complexui.py:863: DeprecationWarning: 
  self.toolbar.append_space()
/var/lib/python-support/python2.5/driconf_complexui.py:872: DeprecationWarning: 
  self.aboutHandler, None, -1)
/var/lib/python-support/python2.5/driconf_complexui.py:873: DeprecationWarning: 
  self.toolbar.append_space()
/var/lib/python-support/python2.5/driconf_complexui.py:876: DeprecationWarning: 
  self.exitHandler, None, -1)
Desktop-Datei file:///home/cai/Desktop/Google-googleearth.desktop konnte nicht für Panel-Starter :  geöffnet werdenNo such file or directory
QDom: saving invalid character &#xdbff;, the document will not be well-formed
QDom: saving invalid character &#xdefc;, the document will not be well-formed
QDom: saving invalid character &#xdbff;, the document will not be well-formed
QDom: saving invalid character &#xdefc;, the document will not be well-formed
Desktop-Datei file:///home/cai/Desktop/Google-googleearth.desktop konnte nicht für Panel-Starter :  geöffnet werdenNo such file or directory
--------------------------------------------------
Traceback (most recent call last):

+ Trace 172559

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-EqkYrxzJYS: Connection refused

Comment 1 Sebastian Pölsterl 2007-10-24 17:54:19 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 ***