Bug#544009: [CRASH] Uncaught exception GError in Frontend/Gtk/ui.py:741

2009-08-31 Thread Miles Bader
Stephan Peijnik deb...@sp.or.at writes:
 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?

I mostly use gnome:  I use gnome-session, gnome-panel, whatever WM
gnome-session starts (used to be metacity, now compiz) and various gnome
apps -- however I _don't_ run nautilus to manage the desktop (i.e., no
icons on my screen, etc).  I dunno how that affects gconf.

My home directory (and thus, I guess, the gconf database) is in NFS, but
/usr is on a local disk.

Thanks,

-Miles

-- 
Immortality, n.  A toy which people cry for, And on their knees apply for,
  Dispute, contend and lie for, And if allowed Would be right proud
  Eternally to die for.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#544009: [CRASH] Uncaught exception GError in Frontend/Gtk/ui.py:741

2009-08-28 Thread Miles Bader
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


*** /tmp/update-manager-bugRebWXw
The information below has been automatically generated.
Please do not remove this from your bug report.

- Exception Type: class 'glib.GError'
- Exception Value: 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://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session: Failed to connect to socket /tmp/dbus-f3eEQeX5Fg: 
Connection refused)',)
- Exception Origin: _MainThread(MainThread, started)
- Exception Traceback:
  File /usr/bin/update-manager, line 38, in module
app.main()
  File /usr/lib/pymodules/python2.5/UpdateManager/Application.py, line 398, 
in main
self._frontend.init_frontend()
  File /usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/__init__.py, 
line 70, in init_frontend
self._ui = GtkUI(self)
  File /usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/ui.py, line 
667, in __init__
self.restore_state()
  File /usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/ui.py, line 
741, in restore_state
gconf.VALUE_INT)




-- System Information:
Debian Release: squeeze/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 
'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages update-manager-gnome depends on:
ii  gconf2 2.26.2-3  GNOME configuration database syste
ii  gksu   2.0.2-2+b1graphical frontend to su
ii  python 2.5.4-2   An interactive high-level object-o
ii  python-dbus0.83.0-1  simple interprocess messaging syst
ii  python-gconf   2.26.1-1  Python bindings for the GConf conf
ii  python-gobject 2.18.0-1  Python bindings for the GObject li
ii  python-gtk22.14.1-3  Python bindings for the GTK+ widge
ii  python-support 1.0.3 automated rebuilding support for P
ii  python-vte 1:0.20.5-1Python bindings for the VTE widget
ii  update-manager-core0.200.0~rc1-2 APT update manager core functional

update-manager-gnome recommends no packages.

Versions of packages update-manager-gnome suggests:
pn  software-properties-gtk   none (no description available)
pn  update-notifier   none (no description available)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#544009: [CRASH] Uncaught exception GError in Frontend/Gtk/ui.py:741

2009-08-28 Thread Stephan Peijnik
#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