This may help tracking down this bug: The ownership is set correctly when using the the "su" method (by calling the "gksu" binary directly instead of of through the "gksudo" symlink AND with the -w option).
This fails: $ gksudo -u firefoxuser firefox No protocol specifiedNo protocol specified Error: cannot open display: :0.0 The following works inspite of the warnings, however the password of the target user is allways required and you can not make use of the NOPASSWORD option in the sudoers file with that. $ gksu -w -u firefoxuser firefox (firefox:3439): GnomeUI-WARNING **: While connecting to session manager: None of the authentication protocols specified are supported. (firefox:3439): GnomeUI-WARNING **: While connecting to session manager: None of the authentication protocols specified are supported. (firefox:3439): GnomeUI-WARNING **: While connecting to session manager: None of the authentication protocols specified are supported. --- It's quite a security shame that ubuntu ships without fully working "running as different user" mechanisms for so long. -- wrong ownership of .Xauthority and /tmp/libgksu-xxx https://bugs.launchpad.net/bugs/275304 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
