KDE file manager problem

[Rog131]

so I guess this will brake the "root actions service menu" that worked so well for editing root owned files

VINNY

Applications need constant love from the developers/maintainers...

 sudoedit --help
sudoedit - edit files as another user

usage: sudoedit [-AknS] [-C num] [-g group] [-h host] [-p prompt] [-u user] file ...

Options:
 -A, --askpass               use a helper program for password prompting
.
.
.

[vinnywright]

so I guess this will brake the "root actions service menu" that worked so well for editing root owned files

VINNY

[Rog131]

Soon

https://blog.martin-graesslin.com/bl...files-as-root/

Posted on 17. February 2017 by Martin Gräßlin

Editing files as root

...Today I pushed a change for Kate and KWrite which does no longer allow to be run as root. Instead it educates the user about how to do the same with sudoedit...

$ sudoedit --help    
sudoedit - edit files as another user

What's So Great About Sudoedit?: http://www.wingtiplabs.com/blog/post...3/13/sudoedit/

[Rog131]

Future?

Title should be: Future ?

nagging: Thread/post title contains prohibited characters! Must match [a-zA-Z0-9.,'-/ ]

Bug 152150 - Cannot 'Open as Root' files/directories : https://bugs.kde.org/show_bug.cgi?id=152150

--> Bug 179678 - Dolphin needs PolicyKit-kde integration in KIO: https://bugs.kde.org/show_bug.cgi?id=179678

KDE File Manager devel mailing list - https://marc.info/?l=kfm-devel&m=148390138125694&w=2

Subject: Looking for co-mentors for a GSoC Dolphin/KIO project

...GSoC 2017 is near and it's time to discuss project ideas.
This year I want to tackle one of the biggest problems in Dolphin:
lack of polkit support. Dolphin users often don't know how to use the
command line, so when they have to move root-owned files around they
are forced to start Dolphin with root permissions, which is bad and
dangerous.

GSoC is a great opportunity and I'm confident we can find an awesome
student who will fix this. ...

[Rod J]

Thanks Kubicle for your interesting explanation of the problem. I thought it wouldn't be so simple to fix it.

[kubicle]

I wish the developers would somehow make it at least difficult to run gui programs with sudo, like a warning message to use kdesudo/gksudo instead or even better to automatically switch to use kdesudo/gksudo as required. I guess it's not so simple to implement this as it would surely have been done by now.

It isn't. It would be extremely hard to find out whether a command will run a GUI app without actually running it, at which point it's too late for sudo to react (like print out a warning or switch to a graphical sudo wrapper).

---

Also, this sudo problem isn't universal. For example, in Debian sudo is compiled to not keep the $HOME environment by default when using sudo, and ubuntu changes this behavior with a patch (which is the root cause for this problem). There are a few reasons for this change in ubuntu, but IMO the benefits don't outweigh the problems the change causes.

---

However, you can also change the default behavior on ubuntu if you wish, with a few ways (after which you can use sudo with GUI apps):

1. Use a command line option that will change the $HOME environment variable to the target user (either -H or -i will work), for example "sudo -i kate" or "sudo -H dolphin"

2. For a permanent change add a new option to sudoers file (either always_set_home or env_keep-="HOME" should change the default behavior)...only do this if you know your way around modifying sudoers, read "man sudoers" or ask for more instructions if you don't.

---

Of course one can also just keep using kdesudo (or other graphical sudo/su wrappers) with GUI apps and use sudo only for CLI commands.

[Rod J]

I wish the developers would somehow make it at least difficult to run gui programs with sudo, like a warning message to use kdesudo/gksudo instead or even better to automatically switch to use kdesudo/gksudo as required. I guess it's not so simple to implement this as it would surely have been done by now.

This sudo + gui app thing is a trap for 'newbies' for sure. I must have done it myself when I first started using Linux years ago.

[Snowhog]

Thanks for the reply. Done!. is this default in kubuntu ?

See RootSudo

[vinnywright]

FYI : this happened because you used "sudo" to get a root dolphin ,,,,you should use "kdesudo" to prevent this

VINNY

[tushar21nov]

The permissions on dolphinrc are incorrect. In a terminal window, do this -

sudo chown tushar:tushar /home/tushar/.config/dolphinrc

good luck!

Thanks for the reply. Done!. is this default in kubuntu ?

[wizard10000]

The permissions on dolphinrc are incorrect. In a terminal window, do this -

sudo chown tushar:tushar /home/tushar/.config/dolphinrc

good luck!

[tushar21nov]

I am using Kubuntu 16.04.1 and it is 64 bit. I am seeing this message when I click on Dolphin file manager to browse other folders and files. I am also unable to make any changes in Dolphin like icon size or options in the menu. This is happening when I log in as a normal user. After click on the OK button or the Close button I can browse Dolphin file manager and other folders and files. How to solve the problem. But I can do anything in root user mode when I use 'sudo dolphin' command in the terminal.

The Message:
Configuration file "/home/tushar/.config/dolphinrc" not writable. Please Contact your System Administrator.