Hi Ralph

On 12/10/12 15:12, Ralph Corderoy wrote:
Hi Tim,

I have various Debian Squeeze machines. Some are running GDM3, but
where possible others have stayed with GDM2. I use XDMCP a lot with
all the machines, and one issue is that any of the Gnome apps (eg root
terminal) that require root authentication fail when logged in to a
GDM3 machine via XDMCP.

So these are things like menu items for Wireshark as root and a Terminal
as root?  It asks for the pleb user's password, like gksu(1), but then
the command fails to run?

Yes, but asks for root's password, not pleb's.

I'm guessing the following in auth.log could be a factor, and there's
some pam setting lurking:

Oct 12 10:42:19 supermicro seahorse-agent[2019]: GConf error:#012
Failed to contact configuration server; the most common cause is a
missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details -  1: Could
not send message to GConf daemon: Connection is closed)

Can you look at seahorse-agent's environment, e.g. `tr \\0 \\n
</proc/.../environ' and see if any of its SESSION variables give a clue.


Well, on the machine I'm testing on this evening I have Gnome and xfce and get the same symptoms with both. With xfce seahorse-agent isn't even running, but gksu is, so I think seahorse is probably a red herring.

There's this in auth.log:

Oct 12 19:59:57 haywood gnome-keyring-daemon[3613]: couldn't access conrol socket: /tmp/keyring-yAY0Ve/control: No such file or directory Oct 12 19:59:57 haywood gnome-keyring-daemon[3613]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files

In seahorse environ:

DESKTOP_SESSION=gnome
GTK_MODULES=canberra-gtk-module
GNOME_KEYRING_CONTROL=/tmp/keyring-Hm6Z39

which is present (logged in to Gnome via XDMCP to get this).

Cheers

Tim






--
Next meeting:  ???, ???day, 2012-11-?? 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread on mailing list:  mailto:[email protected]
How to Report Bugs Effectively:  http://goo.gl/4Xue

Reply via email to