On 2017-06-19 17:48, Wols Lists wrote:
On 19/06/17 16:37, Anton Aylward wrote:
On 19/06/17 05:47 AM, Carlos E. R. wrote:
Running just "su" alone meremly changes your effective UID. By default, it is to root, but could to to another user. It does not alter HOME, SHELL, USER, LOGNAME, and PATH. That last one is important. A real root shell expects to have /sbin & /usr/sbin in the PATH HOME is also very important.
The home is not changed, so that files you write being root (or another user) are written in the user's home. It can thus happen that config files of the user become inaccessible to the user.
that is a very, very good point, Carlos. "Unwanted Side Effects".
That could actually explain what is happening to me :-)
konsole spots that the config file was saved by root, and asks for the root password so it can read it!
I'd be a little surprised if it's that clever, but it does make sense...
No, I doubt it. It would only mess the konsole config files if you start a terminal, do "su", then start konsole from that terminal. If instead you start konsole normally, open a tab, run "su", then some applications, it is that application config or user files which can get messed. But not konsole. Konsole may remember, however, that you had one terminal using "su" and try to start it up for you again, and somehow failing. In any doubt, just search for files owned by root on your home. find /home/YOU/ -type f -uid 0 -exec ls -l '{}' \; -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)