Mageia forum

Hello,

In System Settings under KDE, when systemd actions are performed, like enabling or starting or stopping a service and so on, I get this error:

"Unable to authenticate/execute the action: 4"

However, as root, the same actions can be performed in command line, with systemctl.

What could be the reason?

Thank you!

You may want to ask upstream about that, see https://forum.kde.org/viewtopic.php?f=66&t=88528 and https://bugs.kde.org/show_bug.cgi?id=241817

Hi, I have found those. I don't think those are truly related, because they are for time service only.
My issue is for any command there.
Might be a setting, though. I am asked at any login about a password for the network manager.
Is there a right to be set for my user? Add it to some group?

Hello, I have an update.
Seems it requires a root password for network handling and systemd UI actions (and probably in more similar cases) when remotely connected.
Directly, it does not require password for the network manager, despite it is the same user.
Remotely, it succeeds for the network manager, but not for systemd.

Besides this, resolv.conf is always empty now, not accessing the Internet, as result (can't resolve the addresses...).

Solved the network. I have found that my resolv.conf was symlinked to one in the ppp configuration directory, which was not used anymore (actually deleted the ppp connection with drakconnect --del).
I have deleted the symlink, I have configured the network again, it created the correct resolv.conf and finally works fine.

msdobrescu wrote:Seems it requires a root password for network handling and systemd UI actions (and probably in more similar cases) when remotely connected.

And you didn't want to mention that in your original post?

Hi, on one hand, I am not aware of all the reasons something happens. I mention it when I think it is related.
Also, was a two levels issue.
Until I have removed the connection completely and re-done it from scratch, it asked in any case.

Now, it has a root logon issue when I am remotely connected only, through x2go.
Despite I use the same user in both cases.
Could it be an x2go change, fixable by a configuration?