Bug 1242800 - No Root password is recognized
Summary: No Root password is recognized
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: polkit
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-14 08:23 UTC by antonio montagnani
Modified: 2015-08-31 17:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-31 17:54:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description antonio montagnani 2015-07-14 08:23:24 UTC
Description of problem:

Impossible to update/installa any package as root password is not recognized
Version-Release number of selected component (if applicable):
4.1.3-1 fc22

How reproducible:
always

Steps to Reproduce:
1.try to install any package
2.at the root password window I get an authorization error
3.

Actual results:
authorization error

Expected results:
working as usual

Additional info:

Comment 1 antonio montagnani 2015-07-14 08:36:32 UTC
of course now polkit is 0.113-1

Comment 2 Miloslav Trmač 2015-07-14 15:36:43 UTC
Thanks for your report. 

Does (systemctl restart polkit.service) as root fix this?

Comment 3 antonio montagnani 2015-07-14 15:47:44 UTC
sorry but I can't help you as I installed newest polkit from bodhi. And I do not remember if I rebooted before starting yumex-dnf :-(.

Comment 4 antonio montagnani 2015-07-14 15:48:59 UTC
I have added bob that is suffering same bug

Comment 5 Miloslav Trmač 2015-07-14 15:51:29 UTC
I have received one other report of this, which suggests that restart does work; and there already is an updated 0.113-2 package in bodhi which will cause the restart to happen (i.e. this was already fixed in -1 but only takes effect on -2).

I’m afraid there is no way to accelerate the fix other than giving -2 karma.

Bob, if restarting polkitd does not help, please reopen this bug or comment here.

Comment 6 antonio montagnani 2015-07-14 16:00:28 UTC
Miloslav, on another machine systemctl restart polkit.service works fine (I had forgotten that I am running an additional machine)

Comment 7 Miloslav Trmač 2015-07-14 16:05:44 UTC
Thanks for the confirmation. I apologize about the bug (and I do wonder how I could have missed this) but as explained above the only thing that can help now is giving karma to https://admin.fedoraproject.org/updates/FEDORA-2015-11486/polkit-0.113-2.fc22 . (An independent confirmation that not restarting polkitd and updating to this package works would also be welcome.)

Comment 8 Bob Goodwin 2015-07-14 16:22:34 UTC
I had the problem on two computers, this one is working noramlly after rebboting and removing a dropbox repo that had been causing tro7uble.

However the other oneon which I ran dnf update --exclude polkit does not work. Not after running dnf update to get the polkit update and rebooting a couple of times. Password is still not recognized.

I usually update from command line so I guess I can wait for things to improve?

Bob

Comment 9 Miloslav Trmač 2015-07-14 16:25:14 UTC
(In reply to Bob Goodwin from comment #8)
> However the other oneon which I ran dnf update --exclude polkit does not
> work. Not after running dnf update to get the polkit update and rebooting a
> couple of times. Password is still not recognized.

Interesting.  Can you paste the output of (rpm -qa 'polkit*'), please?

Comment 10 Miloslav Trmač 2015-07-14 20:20:55 UTC
> [root@box7 bobg]# rpm -qa 'polkit*'
> polkit-libs-0.113-1.fc22.x86_64
> polkit-0.113-1.fc22.x86_64
> polkit-gnome-0.105-7.fc22.x86_64
> polkit-pkla-compat-0.1-5.fc22.x86_64

So, everything updated, I have also verified that polkit-gnome as an agent works fine for me.

Is there anything interesting in the logs around the time of the failed password authentication?

Comment 11 Bob Goodwin 2015-08-31 11:11:04 UTC
I have nothing more to add to this.


Note You need to log in before you can comment on or make changes to this bug.