Your message dated Wed, 04 Mar 2009 16:55:03 -0300
with message-id <[email protected]>
and subject line fixed by 2.0.9
has caused the Debian Bug report #511821,
regarding update-manager fails (gconf) when run by update-notifier
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
511821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511821
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: update-manager
Version: 0.68.debian-7
Severity: normal
If I click on the update-notifier icon, I get prompted for my keyring
password as usual, but update-manager doesn't appear, printing the
following error messages in my session log instead. If I run
update-manager from a terminal it works normally.
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://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.)
[above repeated 2 more times]
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")
[First message repeated again]
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages update-manager depends on:
ii gconf2 2.24.0-4 GNOME configuration database syste
ii libgnome2-perl 1.042-1+b1 Perl interface to the GNOME librar
ii python 2.5.2-3 An interactive high-level object-o
ii python-dbus 0.83.0-1 simple interprocess messaging syst
ii python-glade2 2.12.1-6 GTK+ bindings: Glade support
ii python-gnome2 2.22.0-1 Python bindings for the GNOME desk
ii python-support 0.8.7 automated rebuilding support for P
ii python-vte 1:0.16.14-4 Python bindings for the VTE widget
ii software-properties-gtk 0.60.debian-1.1 manage the repositories that you i
ii synaptic 0.62.4 Graphical package manager
ii update-manager-core 0.68.debian-7 APT update manager core functional
update-manager recommends no packages.
Versions of packages update-manager suggests:
ii update-notifier 0.70.7.debian-5 Daemon which notifies about packag
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libgksu
Version: 2.0.9-1
The 2.0.9 release of the library fixes these problems with the new
gconf. I just uploaded it to unstable.
Thanks,
--
Gustavo Noronha <[email protected]>
Debian Project
--- End Message ---
