Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
In the past, I wanted to add a port to kppp (dialer) for my modem driver which made it's own unique port that was not in the list of available ports in kppp. Instead of chasing down a guide or instructions on how to do this I sent an e-mail to the kde team and they responded within a few days telling me I couldn't do it, that saved me a lot of time.
I have an older version of KDE, and noticed in synaptic that there is a package called "kdesudo" which is probably the best route to take at this point for a graphical application that allows you to open other applications as root or another user.
Or you can just set up sudo if you just need to do it from command line.
Slack64-current [KDE4]: Trying to start Konqueror as root is ridiculous. Phooey!
I was about to post a new thread with the above title, but found this one where the issue seems perfectly suited.
The problem *seems* to be something to do with either kdesud or kdeinit4.
I can *eventually* get a root konqueror, but it takes numerous restarts of kdeinit and/or kdeinit4 and maybe the odd `kill -HUP <kdesud PID>` to get a root konqueror to start.
Google shows several reports of the same issue.
What happens:
The first few times I try, kdesu often rejects my root password (though I can `su` from commandline no problem.)
After HUP'ing kdesud, my root password is now accepted, but no konqueror appears.
Sometimes, after trying again two or 3 times, a konqueror will start. If not, try restarting kdeinit and kdeinit4 as both root, and as the user trying to run kdesu.
Sasha
Last edited by GrapefruiTgirl; 08-04-2009 at 10:38 AM.
My girlfriend's running kde4.2 on Debian Squeeze/Sid and the above code works. It takes a moment after you've supplied your root password for konqueror to open up, but it does and in root mode.
edit: [FLASH] She tried it with kdesu and it works too. Just do alt-f2 and type that in.
cheers,
jdk
(remember, Slack has not nearly the Gnome stuff that Debian might)
There is no command 'gksu' or 'gtksu' on my system (Slack64-current), and running it via the ALT-F2 didn't help, BUT thanks for the ALT-F2 tip -- I didn't know of that, and I like that vs. opening a terminal and typung my command there.
@Sasha,
My pleasure. But that's why we tried kdesu afterwards. So even with 0 gnome packages you should be ok. I can't imagine why it would work on hers but not on yours. She's running a 2.6.30 kernel. Could that make a difference?
Cheers,
jdk
the PID shown is that of kdesu. IIRC if/when a konqueror starts as it should, I believe there's no further output on the particular console, but I'll check this next time it starts correctly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.