Description of problem: When trying to check for updates or install them, the following message is shown: "You have failed to provide correct authentication. Please check any passwords or account settings." Version-Release number of selected component (if applicable): apper-0.8.1-1.fc20.x86_64 kde-workspace-4.11.0-4.fc20.x86_64 selinux-policy-3.12.1-73.fc20.x86_64 polkit-0.111-3.fc20.x86_64 polkit-kde-0.99.1-2.20130311git.fc20.x86_64 Fedora 20 Alpha TC2, DVD x86_64 How reproducible: Always Steps to Reproduce: 1. Run Apper 2. Check for updates 3. Actual results: The above message is shown. Expected results: Updates are installed.
Proposing as F20 Alpha blocker per criterion: "The installed system must be able to download and install updates with yum and with the default graphical package manager in all release-blocking desktops.".
Can you check if any 'polkit-kde-authentication-agent-1' process is running?
Yes, polkit-kde-authentication-agent-1 is running.
The user running apper and experiencing this bug * was it set or configured to be an admin user (ie, a member of the wheel group)? * how did you login? via sddm ? If yes, rpm -q sddm please.
(In reply to Rex Dieter from comment #4) > The user running apper and experiencing this bug > > * was it set or configured to be an admin user (ie, a member of the wheel > group)? No. > > * how did you login? via sddm ? If yes, > > rpm -q sddm sddm-0.2.0-0.3.20130821gite707e229 > > please.
Can you (re)test using sddm-0.2.0-0.4.20130821gite707e229.fc20 please?
Discussed at 2013-09-04 blocker review meeting [1]. This is accepted as an Alpha blocker, because it violates the following F20 alpha release criterion for KDE: "The installed system must be able to download and install updates with yum and with the default graphical package manager in all release-blocking desktops." [2] [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-09-04/ [2] https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria#Updates
It seems that sddm-0.2.0-0.4.20130821gite707e229.fc20 fixes the issue.
Thanks for testing.