#bts tag 544009 +confirmed thanks Hi Miles,
Thanks for your bug report. I've just had a look at the code and fixed it in the update-manager code repository. This will be fixed in the upcoming 0.200.0~rc2 release of update-manager, to be uploaded "soon". Oh, by the way, the bug you reported is somehow related to update-manager not being able to contact the gconf server. This could mean that your gconf server is for some reason broken. I have encountered this problem when the update-manager code was on an NFS partition, but I couldn't really reproduce the bug as it didn't occur with every start of update-manager. I am just curious, are you running GNOME or another window manager? Is your /usr partition on NFS? -- Stephan On Fri, 2009-08-28 at 15:44 +0900, Miles Bader wrote: > Package: update-manager-gnome > Version: 0.200.0~rc1-2 > Severity: normal > File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py > > > I don't know exactly what's going on, but update-manager fails to start no > matter how I try to do it (via menu or command line or "sudo update-manager"). > > The error message I get is: > > ------------ start ------------ > $ LANG=C sudo update-manager > error from gconf: Failed to contact configuration server; some possible > causes are that you need to enable TCP/IP networking for ORBit, or you have > stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ > for information. (Details - 1: Failed to get connection to session: Failed > to connect to socket /tmp/dbus-m8W4bKCmdk: Connection > refused)/usr/lib/pymodules/python2.5/UpdateManager/Frontend/GtkCommon/GtkExceptionHandler.py:90: > GtkWarning: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' > failed > res = dialog.run() > dialog result: -8 > Running as root > Detected original user in SUDO_USER env variable > Invoking /usr/share/update-manager/bug_script/debian_reportbug.sh > /tmp/update-manager-bugRebWXw > /usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/ui.py > /tmp/update-manager-bugGCsG7s via gksu as miles > GConf Error: Failed to contact configuration server; some possible causes are > that you need to enable TCP/IP networking for ORBit, or you have stale NFS > locks due to a system crash. See http://projects.gnome.org/gconf/ for > information. (Details - 1: Failed to get connection to session: Failed to > connect to socket /tmp/dbus-TrmqvIvNCL: Connection refused > ------------ end ------------ > > THanks, > > -miles -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
