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 485810 - crash in Deskbar: I had put the tracker ju...
crash in Deskbar: I had put the tracker ju...
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-11 17:47 UTC by webmaster
Modified: 2007-10-12 10:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description webmaster 2007-10-11 17:47:25 UTC 
What were you doing when the application crashed?
I had put the tracker just on the top bar. I wanted to configurate it.


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-rt #1 SMP PREEMPT RT Wed Oct 10 08:24:17 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: WinXP-Silver
Icon Theme: Tango

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 (10074 sec old) ---------------------
alaERROR: 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-7rUpMVPeM3: Verbinding is geweigerd
process 5705: 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.
  PID TTY          TIME CMD
** (update-notifier:5695): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (update-notifier:5695): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (update-notifier:5695): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (update-notifier:5695): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
warning: could not initiate dbus
current dist not found in meta-release file
--------------------------------------------------
Traceback (most recent call last):

+ Trace 169557

  • 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-7rUpMVPeM3: Verbinding is geweigerd 






Comment 1


Sebastian Pölsterl





          2007-10-12 10:24: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 ***