GNOME Bugzilla – Bug 487858
crash in Deskbar: logging in
Last modified: 2007-10-18 13:01:38 UTC
What were you doing when the application crashed? logging in 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-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (32 sec old) --------------------- Starting gtk-window-decorator ** Message: Not starting remote desktop server Initializing gnome-mount extension (gnome-panel:7072): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80f3960 (gnome-panel:7072): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80f3960 inotify_add_watch: No such file or directory ** (nm-applet:7121): WARNING **: <WARN> nma_dbus_device_properties_cb(): dbus returned an error. (org.freedesktop.DBus.Error.NoReply) Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeo libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.NoReply) Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeo -------------------------------------------------- Traceback (most recent call last):
+ Trace 171108
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
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 474179 ***