You are not logged in.

#1 2017-04-29 21:09:55

Potomac
Member
Registered: 2011-12-25
Posts: 528

[solved] kdesu doesn't work, no launch and no error message in logs

Hello,

I made a full update of my system,

and I notice that kdesu doesn't work,

for example I type:
kdesu kate

a window asking my password is displayed, I type my passwork, I click "ok" but there is no "kate", nothing,

and there is no error message in logs ( dmesg ) and no error message in console,

Do you know if an alternative to kdesu exists for running GUI program in root mode ?

Last edited by Potomac (2017-04-29 21:55:17)

Offline

#2 2017-04-29 21:20:16

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,672

Re: [solved] kdesu doesn't work, no launch and no error message in logs

kdesu works, the KDE programs (kate and dolphin etc) have been adjusted to not be allowed to run as root anymore, because of several security concerns of allowing a root context to connect to an X11 server. The better alternative, would be using e.g. sudoedit to edit text files and add kate to your EDITOR environment variable. that way you can edit text files without starting the whole editor as root. If you absolutely want to use a GUI text editor you will have to look at alternatives. Afaik KDE programs will at some point have polkit integration where they will dynamically ask for privilege escalation,  but that isn't part of a released software yet.

Edit: As has been mentioned, frameworks 5.34 now has polkit integration, works fine here, open a file in kate and edit away you will be prompted to authenticate on save

Last edited by V1del (2017-05-25 11:25:39)

Offline

#3 2017-04-29 21:25:13

PootisBird
Member
Registered: 2014-04-16
Posts: 125

Re: [solved] kdesu doesn't work, no launch and no error message in logs

Kdesu is not a secure method and it is being phased out. Runing X applications as root is considered dumb by some KDE devs. Your best bet is sudoedit.
You need to set VISUAL and/or EDITOR in your bashrc.

At least for dolphin breaking kdesu was a deliberate security decision, not sure about kate.

Edit. Sniped.

Last edited by PootisBird (2017-04-29 21:25:46)

Offline

#4 2017-04-29 21:34:17

Potomac
Member
Registered: 2011-12-25
Posts: 528

Re: [solved] kdesu doesn't work, no launch and no error message in logs

thanks for yours answers,

I will try another alternative, maybe sudoedit or another GUI notepad

Offline

#5 2017-04-29 21:36:35

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [solved] kdesu doesn't work, no launch and no error message in logs

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title (and remove the redundant [kdesu]).


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#6 2017-04-29 21:36:49

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 2,098

Re: [solved] kdesu doesn't work, no launch and no error message in logs

With frameworks 5.34 it will be possible to edit root owned files without having to run kate as root. Until then, use sudoedit as V1del and PootisBird said

Offline

#7 2017-05-05 02:16:39

edoantonioco
Member
Registered: 2015-04-15
Posts: 3

Re: [solved] kdesu doesn't work, no launch and no error message in logs

Is arch going to offer a solution for this? Artengos for example created a dolphin-root package to deal with this, what about arch?

The other solution for this would be to use the terminal, and that would be a step back

Offline

#8 2017-05-05 02:20:27

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,544

Re: [solved] kdesu doesn't work, no launch and no error message in logs

You want a "solution" for an upstream decision to prevent people from doing something stupid? Don't hold your breath.

Offline

#9 2017-05-05 15:30:00

c00ter
Member
From: Alaskan in Washington State
Registered: 2014-08-28
Posts: 394

Re: [solved] kdesu doesn't work, no launch and no error message in logs

It really boils down to the question of is the user willing to accept a different, more secure method of accessing and altering critical system files?

Antergos' solution intimates the answer is, "No, the users are not willing, so we will make them happy" and this solution should work until a future upgrade when their solution creates havoc and we have their users posting here seeking a solution to a problem that Arch did not impose to begin with.

There is nothing we can do to prevent users harming themselves. If they insist on running with scissors they should already be aware of the dangers involved.

Other than that, I agree with my signature line.

Last edited by c00ter (2017-05-05 15:31:10)


UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

Offline

Board footer

Powered by FluxBB