Bug#582824: Sorry, this bug is not fixed

Dominique Brazziel dbrazziel at snet.net
Wed Jul 7 19:36:14 UTC 2010


	Clicking on a bug link still fails with the exact messages in
'.xsession-errors' I noted above.  Once I changed gksu to operate in
'sudo mode' the errors went away and the bug reports were displayed.
	
	Then I changed gksu back to default mode, and changed 
'/usr/share/pyshared/UpdateManager/Frontend/Gtk/__init__.py' to
call gksu in sudo mode by adding the '-S' flag and links worked again.

	Here is a comparison of the processes invoked with and with 
sudo mode:

Without sudo mode (fails with 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
cr
ash. 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 erro
r: No protocol specified
Autolaunch error: X11 initialization failed.)
-------------------------------------------------------------------------
1000     19191     1  4 15:21 ?
00:00:00   /usr/bin/python /usr/bin/update-manager
1000     19197 19191  0 15:21 ?        00:00:00     /usr/bin/gksu -k
-D /usr/share/applications/update-manager.desktop
-- /usr/bin/update-manager
root     19202 19197  0 15:21 pts/12   00:00:00       /bin/su root -p
-c /usr/lib/libgksu/gksu-run-helper "/usr/bin/update-manager"
root     19213 19202  0 15:21 pts/12
00:00:00         /usr/lib/libgksu/gksu-run-helper /usr/bin/update-manager
root     19217 19213  0 15:21 pts/12   00:00:00           sh
-c /usr/bin/update-manager
root     19218 19217 40 15:21 pts/12
00:00:04             /usr/bin/python /usr/bin/update-manager


With sudo mode (success)
------------------------
1001     18321 18316  0 15:09 ?        00:00:00     /usr/bin/gksu -S -k
-D /usr/share/applications/update-manager.desktop
-- /usr/bin/update-manager
root     18322 18321  0 15:09 ?
00:00:05       /usr/bin/python /usr/bin/update-manager
1001     18360 18322  0 15:09 ?        00:00:00         [gnome-open]
<defunct>

I think the problem has something to do with trying to execute
gnome-open as root but the current environment (including the
DBUS_SESSION_BUS_ADDRESS) is for the login user.   







More information about the pkg-gnome-maintainers mailing list