Root konsole; Sorry - Plasma!

[hallergard]

Editing konsole in the menu and running gives these 'Sorry - Plasma' error messages:
sudo konsole KDEInit could not launch '/usr/bin/sudo'
kdesu konsole KDEInit could not launch '/urs/lib/x86_64-linux-gnu/libexec/kf5/kdesu
Help would be appreciated!

[elijathegold]

Have you tried kdesudo konsole?

[hallergard]

Thanks! Have now: kdesudo konsole KDEInit could not launch '/urs/lib/x86_64-linux-gnu/libexec/kf5/kdesu

[elijathegold]

There appears to be a bug which, for some applications, can be worked around by running sudo ln -s /usr/bin/kdesudo /usr/bin/kdesu and I guess using kdesu konsole.

Bug report

[hallergard]

Thanks, but no luck!

[elijathegold]

If you are trying to have root konsole, then change the command in the menu entry to konsole -e sudo -s which will ask for your password inside konsole

[hallergard]

Great, that did the trick! Actually I was looking for a way not to have to enter my password inside konsole (group wheel and and superuser in kdesurc) - and I don't have to now with konsole -e sudo -s
Thanks again!

[kubicle]

Great, that did the trick! Actually I was looking for a way not to have to enter my password inside konsole (group wheel and and superuser in kdesurc) - and I don't have to now with konsole -e sudo -s
Thanks again!

You generally should not use "sudo -s" as it will leave the $HOME environment variable pointing to your user's home directory which can lead to all sorts of problems. Use "sudo -sH" or "sudo -i" instead. You can check the $HOME variable in the shell with "echo $HOME"

[elijathegold]

In my case, that's the desired behaviour., but use sudo -sH as sudo -i gives an error that the current user in unavailable.

[kubicle]

In my case, that's the desired behaviour.

You can get away with it if you know what you're doing (and understand what it means).
Possible problems of course depend on what you do in the shell, but generally it's safer to have a "full" root environment in a root shell.

sudo -i gives an error that the current user in unavailable.

It shouldn't do that.

[elijathegold]

You can get away with it if you know what you're doing (and understand what it means).
Possible problems of course depend on what you do in the shell, but generally it's safer to have a "full" root environment in a root shell.

Yeah I know.

It shouldn't do that.

I've just remembered why it does but I'm not going to elaborate because it's too embarrassing. Safe to say that sudo -i should be fine.

[hallergard]

Tried -si but it did not work for me either, so I am now using -sH. Wonder what I am supposed to be embarressed about?

[elijathegold]

Suffice it to say that I was configuring when I shouldn't have been and made a huge error; before I thought it through, I enabled the root user. It turned out that I didn't help so I then locked it out with the usermod -l command. Since then sudo -i hasn't even worked within a terminal session.

I might get round to fixing it one of these days.

Also sudo -i or sudo -sH not sudo -si

[hallergard]

Right, sudo -i works for me, thanks