Patrick Wiseman wrote: > On Fri, Mar 13, 2009 at 11:10 AM, JoeHill <joeh...@teksavvy.com> wrote: > > > > All of a sudden-like, my update applet doesn't work properly. If I give it a > > click, I am asked for the root pass as usual, but then nothing happens. > > > > Nothing. > > Open a root terminal and run 'update-manager' and I'll bet you'll see > a GTK authorization error.
Forgot this part...you are correct: node1:/home/joehill# update-manager warning: could not initiate dbus Traceback (most recent call last): File "/usr/sbin/update-manager", line 76, in <module> app = UpdateManager(data_dir) File "/var/lib/python-support/python2.5/UpdateManager/UpdateManager.py", line 400, in __init__ self.restore_state() File "/var/lib/python-support/python2.5/UpdateManager/UpdateManager.py", line 831, in restore_state expanded = self.gconfclient.get_bool("/apps/update-manager/show_details") gobject.GError: 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://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: 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 timeout expired, or the network connection was broken.) > My workaround until it's fixed is to use the applet just to tell me when > there are updates available and then to run aptitude! (I realize that's > totally unsatisfactory!) -- J -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org