Authentication failed

Hello,
normally I use Manjaro, but I also like to test other distributions. That's how I ended up on Garuda XFCE. However, I noticed a problem right away: via pacman/yay I can easily install software. So the administrator password obviously works. However, if I select "Add Software" option in the Start menu (i.e. via the GUI) programs, I get the "Authentification failed" message. The root password is not requested. Does anyone know why I can install software via the terminal and not via the GUI ? I can update the system via pacman -Suy without problems.

Probably polkit isnt running

Try logging out then login

2 Likes

And Welcome

3 Likes

Log out and login are working ... but on every start its same i need to log out and log in again to fix it ..
gives any way to fix it permanent ?
(de is cinamon at me )

Try this in terminal and report back.

systemctl status polkit

You may need to activate it with.

systemctl enable polkit
systemctl start polkit
1 Like

systemctl status polkit gives this
❯ systemctl status polkit ─╯
● polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
Active: active (running) since Thu 2020-10-29 16:53:37 CET; 30s ago
Docs: man:polkit(8)
Main PID: 726 (polkitd)
Tasks: 12 (limit: 77018)
Memory: 29.7M
CPU: 205ms
CGroup: /system.slice/polkit.service
└─726 /usr/lib/polkit-1/polkitd --no-debug

Okt 29 16:53:37 smoky-GarudaLinux systemd[1]: Starting Authorization Manager...
Okt 29 16:53:37 smoky-GarudaLinux polkitd[726]: Started polkitd version 0.118
Okt 29 16:53:37 smoky-GarudaLinux polkitd[726]: Loading rules from directory /e>
Okt 29 16:53:37 smoky-GarudaLinux polkitd[726]: Loading rules from directory /u>
Okt 29 16:53:37 smoky-GarudaLinux polkitd[726]: Finished loading, compiling and>
Okt 29 16:53:37 smoky-GarudaLinux systemd[1]: Started Authorization Manager.
Okt 29 16:53:37 smoky-GarudaLinux polkitd[726]: Acquired the name org.freedeskt>
lines 1-18/18 (END)

the other comands
❯ systemctl enable polkit ─╯
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ====
Authentication is required to manage system service or unit files.
Authenticating as: smoky
Password:
==== AUTHENTICATION COMPLETE ====
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

    ~                                                                                                                                                                  took 4s   0.87   6%   56.72G   0B   at 04:57:06   ─╮
❯ systemctl start polkit                                                                                                                                                                                                                   ─╯
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Legitimierung ist zum Starten von »polkit.service« notwendig.
Authenticating as: smoky
Password: 
==== AUTHENTICATION COMPLETE ====

But still same error

It's loading on boot. Not sure what to add.

1 Like

Perhaps try installing an alternate version of Pamac from the AUR using Yay.

2 Likes

THX .. but even with pamac-aur its same

You could try alternate GUI package managers just to narrow down if this is a pamac issue. Unfortunately, you're using Xfce so any other GUI apps will likely bring in a bunch of dependencies.

discover have same problem
octupi works

Very strange.

Does it do this from the live boot as well?

If it works on the live disk, then either an update has broken something or it's a result of user intervention.

If it works on the live disk, then you've got some real work to track which update caused it.

The other possibility is some configuration file change on your part could have caused this, or perhaps a program you installed is causing some conflict. What have you installed from the AUR?

The only other thing I can suggest is to start Pamac or Discover from the terminal and post any errors they output. You also might want to search your journal for errors when you were trying to install with pamac/discover.

1 Like

ok i just try on live disk there is no problem
pacman on terminal no problem also only with gui
but i think i better make a new install
Thx for u help

1 Like

4 posts were merged into an existing topic: /usr/lib/polkit-kde-authentication-agent-1

I'm getting the blow when I attempt the above quoted. Any suggestions on correcting this? Thanks

Garuda Linux 5.9.10-zen1-1-zen x86_64
    ~          1.82   19%   18.92G   0B   at 09:50:42 AM  ─╮
❯ systemctl enable polkit                                                 ─╯
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ====
Authentication is required to manage system service or unit files.
Authenticating as: Whacker (whacker)
Password: 
==== AUTHENTICATION COMPLETE ====
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

    ~ 
❯ systemctl start polkit                                                  ─╯
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to start 'polkit.service'.
Authenticating as: Whacker (whacker)
Password: Failed to start polkit.service: Connection timed out
See system logs and 'systemctl status polkit.service' for details.

    ~ 
❯ polkit-agent-helper-1: pam_authenticate failed: Permission denied       ─╯

What were you doing to get the error before trying the above?

2 Likes

Just updates. It's why I chose to go ahead and do the updates via Discover. Now I did take the one bit of advice from above and try another logoff / on and that seems to have fixed it for now. I've install a few items using Pamac since my post. Other than this all looks good and not seeing any other issues.

1 Like

Looks like the issue is still there after a reboot. Long story short I did what I was going to do for the day yesterday and booted Gary back into Manjaro. This morning I'm in the process of adding his software, tweaking Dolphin, and fixing his mount points.

I moved all his mounts to /mnt/ and all looked good. I did a reboot and notice Music wasn't mounted, so I launched Disk to see if I forgot to check mount on start. I checked it, clicked ok and was presented with.

Error updating /etc/fstab entry
Not authorized to preform operation (udisk-error-quark,) 

On a hunch I decide to attempt to do the handful of updates with Pamac and sure enough I got the one error from my post yesterday. I did a logoff and on and both are working once again. So it looks like this and the error one gets when trying to update are related. Looks like there may be needed a bit deeper trouble shooting on this. Any help and or suggestions would be greatly appreciated. Thanks

Got the same error last night and this morning with openbox on Arch with pamac. Never got by it yet myself.

1 Like

Have you both tested alternate kernels. The best thing for you both to do is figure out a commonilty you share.

Is this an external drive that's having
the problem?

Are the drives involved NTFS, ext4, btrfs formatted?

Which kernels are you using?

Which I/O schedulers are you using?

Have you checked your logs for errors and searched any error codes online for hits?

Etc, etc,... etc.

1 Like