In my /etc/sudoers, I have something like that: mainuser ALL = (user2) NOPASSWD: /path/to/program so that I can do gksudo -u user2 /path/to/program and execute the (graphical) program as user2 without having to enter my password. When I upgraded x11-libs/libgksu from 2.0.9 to 2.0.12, this stopped working. It always prompts for my password. Reproducible: Always
Please take a look on patch from: http://bugs.gentoo.org/show_bug.cgi?id=290733#c6 Good luck!
Yes, your patch solves the issue with 2.0.12
OK, thanks a lot for trying it :-) Dang, Gnome Team, please take a look on patch http://bugs.gentoo.org/show_bug.cgi?id=290733#c6 A summary about the problem can be seen from http://bugs.gentoo.org/show_bug.cgi?id=290733#c3 Sorry a lot to people affected as I was the culprit suggesting libgksu update wrongly, as I don't use sudo at all and only use gksu for opening root apps using "su" instead Now, I am not sure about reverting 2.0.12 to testing or simply stable directly a 2.0.12-r1 release including the patch, as patch seems to simply revert to 2.0.9 sudo behavior and is used for months under ubuntu (that still uses gksu a lot) without problems
Probably patch and quick-stable a -r1. I don't have time to look at this today; maybe someone will beat me to it?
So you can swiftly mark libgksu-2.0.12 as unstable so it doesn't get installed (like it did again in my case when emptying the tree) and the bug doesn't reappear!
I've been using 2.0.12+patch for a little more than 3 weeks now with now problems whatsoever. I propose to do what Daniel suggested (comment #4).
For the record, I can't reproduce this problem at all. with my setup or with example in bug report, once I typed the password once, it won't ask me again. Maybe this is not only related to libgksu ?
(In reply to comment #7) > ... once I typed the password once ... The problem appears when you have the NOPASSWD option in your sudoers. With this option it should not ask for a password at all.
Is this problem solved since the resolution of bug #298289 (libgksu-2.0.12-r1 ?)
(In reply to comment #9) > Is this problem solved since the resolution of bug #298289 (libgksu-2.0.12-r1 > ?) > Yes, with libgksu-2.0.12-r1 everything works as expected.
Thanks. *** This bug has been marked as a duplicate of bug 298289 ***