SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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: 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:
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.
I got gksu to work using the root password by doing the following:
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 04:01 PM.
Reason: partially working now