Bug#588354: update-manager-gnome: Changlog viewer bug click fails with GConf error

Wed Jul 7 16:51:01 UTC 2010

Package: update-manager-gnome
Version: 0.200.4-1
Severity: important

    Click on a bug link, bug report doesn't open up in browser.
The following appears in '.xsession-errors':

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: /usr/bin/dbus-launch terminated
 abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
)
Error showing url: Operation not supported

This appears to be some sort of Dbus error but dbus-daemon is indeed running.
The error is currently occurring in a remote VNC session which I just restarted, so there
are fresh instances of 'gnome-settings-deamon', 'dbus-daemon' and anything else I can
think of that u-m would need.

It's also happening on my local machine, I started it with the --debug switch, am
attaching the output.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages update-manager-gnome depends on:
ii  gconf2                        2.28.1-3   GNOME configuration database syste
ii  gksu                          2.0.2-3    graphical frontend to su
ii  python                        2.5.4-9    An interactive high-level object-o
ii  python-dbus                   0.83.1-1   simple interprocess messaging syst
ii  python-gconf                  2.28.1-1   Python bindings for the GConf conf
ii  python-gobject                2.21.1-2   Python bindings for the GObject li
ii  python-gtk2                   2.17.0-2   Python bindings for the GTK+ widge
ii  python-support                1.0.8      automated rebuilding support for P
ii  python-vte                    1:0.24.1-1 Python bindings for the VTE widget
ii  update-manager-core           0.200.4-1  APT update manager core functional

update-manager-gnome recommends no packages.

Versions of packages update-manager-gnome suggests:
ii  software-properties-gtk  0.60.debian-1.1 manage the repositories that you i
ii  update-notifier          0.99.3debian4   Daemon which notifies about packag

-- no debconf information
-------------- next part --------------
[   DEBUG:UpdateManager.Application] Loglevel set to debug.
[   DEBUG:UpdateManager.Application] [nonroot] Root privileges required.
[   DEBUG:UpdateManager.Frontend.Gtk] Spawning new update-manager process via gksu.
[   DEBUG:UpdateManager.Application] Loglevel set to debug.
[   DEBUG:UpdateManager.Application] [got-root] Frontend uses privileged functions.
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock acquired.
[   DEBUG:UpdateManager.BugHandler] Installed exception handler <class 'UpdateManager.Frontend.GtkCommon.GtkExceptionHandler.GtkExceptionHandler'>.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] No listening object (org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UpdateManager was not provided by any .service files)
[   DEBUG:UpdateManager.Frontend.Gtk.ui] GtkDbusController initialized.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Stored launch time via gconf.
[   DEBUG:UpdateManager.Frontend.Gtk.GtkProgress] GtkOpProgress initialized.
[   DEBUG:UpdateManager.Frontend.Gtk.GtkProgress] Changing to hidden mode.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] State restored.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Main window made visible.
[   DEBUG:UpdateManager.Application] Reloading the package cache.
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock released.
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock acquired.
[   DEBUG:UpdateManager.Frontend.Gtk.GtkProgress] Cache loading finished.
[   DEBUG:UpdateManager.Frontend.Gtk.GtkProgress] Cache loading begin.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Updating treeview.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Update list store cleared.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Busy status set.
[   DEBUG:UpdateManager.Backend.PythonApt] openoffice.org-core conflicts with itself (<PackageDependency: openoffice.org-core (1 1:3.2.1-3))
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock acquired.
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock released.
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock acquired.
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock released.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Busy status cleared.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Changelog not in cache, need to download (avahi).
[   DEBUG:UpdateManager.DistSpecific.changelog] Fetching changelog entry for avahi-daemon.
[   DEBUG:UpdateManager.DistSpecific.changelog] Getting changelog URL for package <PackageInfo: avahi-daemon>
[   DEBUG:UpdateManager.DistSpecific.Debian.changelog] Downloading changelog for avahi from http://packages.debian.org/changelogs/pool/main/a/avahi/avahi_0.6.25-4/changelog.txt.
[   DEBUG:UpdateManager.DistSpecific.changelog] Fetching http://packages.debian.org/changelogs/pool/main/a/avahi/avahi_0.6.25-4/changelog.txt...
[   DEBUG:UpdateManager.DistSpecific.changelog] Found double-dash sequence, closing stream.
[   DEBUG:UpdateManager.Util.procesinfo] Proc: <ProcessInfo(pid=6114, name=sh, owner_uid=0, parent_pid=6110)
[   DEBUG:UpdateManager.Util.procesinfo] Proc: <ProcessInfo(pid=6110, name=gksu-run-helper, owner_uid=0, parent_pid=6100)
[   DEBUG:UpdateManager.Util.procesinfo] Proc: <ProcessInfo(pid=6100, name=su, owner_uid=0, parent_pid=6092)
[   DEBUG:UpdateManager.Util.procesinfo] Proc: <ProcessInfo(pid=6092, name=gksu, owner_uid=1000, parent_pid=6084)
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: /usr/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
)
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: /usr/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
)
Error showing url: Operation not supported
[   DEBUG:UpdateManager.Frontend.Gtk.ui] State saved.
[   DEBUG:UpdateManager.Frontend.Gtk.ui] Exiting.
[   DEBUG:UpdateManager.Frontend.GtkCommon.SimpleGtkbuilderApp] Exit event received.
[   DEBUG:UpdateManager.Backend.PythonApt] Package system lock released.
[   DEBUG:UpdateManager.Application] Frontend exited with status 0.