SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
yes, i noticed that one, but that one uses sudo and it requires users to change /etc/sudoers
while this worked for MATE 1.6, probably it will not work with MATE 1.8 since mate-file-manager-gksu is now merged along with other mate-file-manager plugins to a single caja-extensions package
Why wouldn't it work with mate 1.8? If it needs gksu, it will work with the gnsu package. If it doesn't need gksu, then you don't have a problem in the first place. The way you package the extension, as a single package or in package that includes multiple extensions, makes absolutely no difference.
willysr, would you be willing to test my shadow patches (one at a time) to see if that resolves the OP's report? If I'm right, re-building shadow with either patch should solve this issue.
@willysr: Many thanks for testing things but it seems your system is non-standard enough to make troubleshooting a bit more challenging (too many variables). It will probably be more efficient if I work directly with the OP.
@aszabo: I know you've fixed your problem by using gnsu (sudo frontend) instead of gksu (su frontend). However, it would be valuable if you would temporarily revert to your original setup (where gksu was failing) and upgrade your shadow package with my patched version. I have placed the full set of files needed for building here.
The only changes I've made to Slackware's 14.1 shadow source files are: 1) editing shadow.Slackbuild so my patch is applied and changing the package name to include a "_mancha" suffix and 2) including my two patches (only one is applied).
Please let me know if this changes your gksu behavior. Thanks.
Hi, the problem is solved with your pathed shadow package, many thanks for it.
Many thanks for confirming my suspicion your issue was related to "su -c" dropping the controlling tty. I've started a thread which discusses "su -c" and will reference this as another example of breakage.
If you're willing to spend a bit more time troubleshooting, it would be good if you rebuilt shadow using the "relax" patch instead of "revert" by changing line 74 of shadow.SlackBuild from:
hi mancha,
I applied your patch and I still get this error: The gksu-run-helper command was not found or is not executable. (when I Alt+f2 gksu thunar) however, running gksu will bring up a window that prompts me to enter the command and user and it seems to run fine. Any ideas as to how I can get the Alt+f2 function to work?
thanks in advance.
--scarrs
EDIT
I got gksu to work using the root password by doing the following:
mkdir /usr/lib/libgksu
ln -s /usr/lib64/libgksu/gksu-run-helper /usr/lib/libgksu/gksu-run-helper
is this acceptable or is it me and I should be able to enter my user passwd instead of the root passwd?
Last edited by scarrs; 02-13-2014 at 03:01 PM.
Reason: partially working now
hi mancha,
I applied your patch and I still get this error: The gksu-run-helper command was not found or is not executable. (when I Alt+f2 gksu thunar)
Hi. Your issue is unrelated to the one solved with my Shadow patch.
But I downloaded gksu, libgksu, and libgtop from SBo to see if I could help. I can reproduce your issue on x86_64 Slackware and tracked down the problem.
The patch I prepared corrects things. Place it in the "patches" dir, make the following change to the SlackBuild script, and rebuild:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.