Bug 398367 - Authentication dialog does not accept password of admin user on root-locked Ubuntu-based system
Summary: Authentication dialog does not accept password of admin user on root-locked U...
Status: REPORTED
Alias: None
Product: policykit-kde-agent-1
Classification: Plasma
Component: general (show other bugs)
Version: 5.13.5
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Jaroslav Reznik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-07 16:12 UTC by 13hurdw
Modified: 2021-11-18 12:43 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Authentication fails on admin password (31.27 KB, image/png)
2018-09-07 17:27 UTC, 13hurdw
Details

Note You need to log in before you can comment on or make changes to this bug.
Description 13hurdw 2018-09-07 16:12:19 UTC
Neon user edition
polkit-kde-agent-1/xenial,now 4:5.13.5-0xneon+16.04+xenial+build64 amd64

To reproduce:
  - In a limited user account session, open software updates in discover.
  - Click "Update All"
  - Enter password of admin/sudo user

Expected:

Dialog takes the admin/sudo user password to unlock privileges.


Actual:

Dialog asks "Password for root:", shows Authentication failure when the admin user password is entered. This won't work on Ubuntu because the root user is locked by default.


This bug makes updating through discover software updates impossible on KDE Neon (in a standard user session).
Comment 1 13hurdw 2018-09-07 17:27:25 UTC
Created attachment 114833 [details]
Authentication fails on admin password
Comment 2 J Saunders 2021-09-02 21:55:44 UTC
Manjaro Plasma OS ask for "Authentication" password when I didn't require (2FA). Using the "TIME-SHIFT" app, I cannot access it without the password? How can I bypass this, so that I can activate a (snapshot) in Time-shift that works?
Thanks!
Comment 3 Zhelyazko 2021-10-01 12:03:46 UTC
I have started to experience this on Kubuntu 20.04 LTS recently, maybe 2-3 weeks ago. Initially it didn't click as a problem as I often work/update via the terminal, but after a few occurrences, I started to search for this issue on the Internet. I have to say that I don't recall doing anything special that could trigger this, just everyday work and periodic updates via apt.