Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
The KDE team seems to have had a brainstorm and have disabled Dolphin from being run as root. It also seems that they intend to extend this to editors.
In other words they have removed a vital freedom from users.
I would like to stay with Plasma but this restriction is a crippling one. Does anybody know a way to circumvent this restriction?
Which distribution are you using? You should be able to open a terminal and do: kdesu dolphin
OR: export $(dbus-launch) (hit the enter key) type: dolphin to open it
Which distribution are you using? Don't know that it will work on all so you just need to test as both work for me with kde5.
The KDE team seems to have had a brainstorm and have disabled Dolphin from being run as root. It also seems that they intend to extend this to editors.
In other words they have removed a vital freedom from users.
For those using a new version of Plasma 5/ Dolphin there has been a move away from running Dolpinh as root, but allowance has been made to configure Dolphin to allow various actions on root-owned files instead....
Rather than seeking to launch Dolphin as root, which i presume you wish to do so as to perform root actions on files & directories owned by root not you, why not actually use Dolphin's native Root Actions capability? Mint 17.x KDE has this, & i loved it, but stupidly they omitted it from Mint 18 KDE [as did also Kubuntu 16.04, KFedora 24, & even KDE Neon itself, but it's present by default & working beautifully in Maui]. This is one of the major reasons [though there's many others too] that last year i abandoned Mint KDE & came over to Maui.
You can configure Root Actions via Dolphin's Configure Dolphin menu selection:
The KDE team seems to have had a brainstorm and have disabled Dolphin from being run as root. It also seems that they intend to extend this to editors.
In other words they have removed a vital freedom from users.
I would like to stay with Plasma but this restriction is a crippling one. Does anybody know a way to circumvent this restriction?
I am running Plasma on Debian unstable.
Yes your right it is in the code when user ID 0 starts it it will stop. You can patch it or set the user ID to 999999999 like I did rebuild it you get a out of range warning but it is fixed.
Alien Bob developer for Slackware has been patching it. Slackware uses root. Top user should be able to use the computer.
I could not do it using Dolphin, like I have been doing since dinosaurs walked the earth.
I always do:
1. Delete firefox.bak
2. Rename Firefox to Firefox.bak
3. Open the new archive.
4. Extract to /usr/local.
Since /usr/local is owned by root I had to jump through hoops and then use krusader. One can commend Martin Floser's enthusiasm but his autocratic behaviour is unacceptable. I am surprised that this change was allowed to go through. Where has our Freedom gone? Or should we drop the "F" from "FOSS"?
Yes your right it is in the code when user ID 0 starts it it will stop. You can patch it or set the user ID to 999999999 like I did rebuild it you get a out of range warning but it is fixed.
Alien Bob developer for Slackware has been patching it. Slackware uses root. Top user should be able to use the computer.
Can you point me towards some more detailed instructions please? I get what you are saying but don't know how to set about doing it.
I can run [URL="https://en.wikipedia.org/wiki/Midnight_Commander"]Midnight Commander (mc)[/URL. It's a dual-pane ncurses file manager similar to the old Norton Commander from the DOS days.
I can run mc as root in Debian Sid. If I try to run Dophin, I get an "it is forbidden" warning. The "export dbus" error message does not appear. When I try to "export dbus," I get a"forbidden to user ID less than 1000" message.
I agree that this is an unnecessary and annoying decision that addresses an issue that I doubt actually exists.
@frankbell: Are you able to configure Doplhin (services) to permit root actions as described in post #4?
I have not tried that yet. Anything I do as root I generally do from the command line, not because I'm expert, because making mistakes is how I learn.
I used to run Konqueror from time to time as root so as to configure directory permissions for Samba shares. which was about the only reason I ever ran a file manager as root, because it was easy.
I may play around with the suggestion in post #4, but I probably won't get to it for a few days; tomorrow is already booked, for we are going to a Christmas concert, hoping it will lift our spirits! If I do try that suggestion, I shall certainly report back.
Also, I am not a Dolphin fan. As you can conclude from the above, I prefer to use Konqueror as a file manager and never have figured out why KDE came up with Dolphin when Konqueror worked so very nicely, thank you very much.
Also, he added facetiously, why is it called "Dolphin"? This is KDE we're talking about here. Shouldn't it be called "Karp"?
I have not tried that yet. Anything I do as root I generally do from the command line, not because I'm expert, because making mistakes is how I learn.
Yes, I generally prefer the CLI too, but I think most experienced users would be in this category. (The need to run Dolphin as root goes away if root actions can be enabled though.)
Quote:
I may play around with the suggestion in post #4, but I probably won't get to it for a few days; tomorrow is already booked, for we are going to a Christmas concert, hoping it will lift our spirits! If I do try that suggestion, I shall certainly report back.
Seasons greetings! I look forward to reading about your findings here.
Quote:
Also, he added facetiously, why is it called "Dolphin"? This is KDE we're talking about here. Shouldn't it be called "Karp"?
#ifndef Q_OS_WIN
// Check whether we are running as root
if (getuid() == 0) {
std::cout << "Executing Dolphin as root is not possible." << std::endl;
return EXIT_FAILURE;
}
#endif
I tried the suggestions in post #4 on Debian Sid with the Plasma desktop.
The "Root Actions" was not present in my version of Dolphin in Plasma on Debian Sid. It may be available via a plugin, but I haven't been able to explore that fully.
I tried the suggestions in post #4 on Debian Sid with the Plasma desktop.
The "Root Actions" was not present in my version of Dolphin in Plasma on Debian Sid. It may be available via a plugin, but I haven't been able to explore that fully.
frank it would be imposible like you said. do to the fact they use sudo and have no reason to let a user become "0".
I looked at the deb source and it is right from kde. why would they patch it. they have no reason to be root
Mewwwy qwissmass fwank
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.