After some recent update, the Software Updates plasmoid (or whatever it’s called – the thing that runs runs from the task bar) no longer works. When packagekitd runs periodically, the following messages appear as two different popups in the notification section on the screen:
Authorization failed You have failed to provide correct authentication. Please check any passwords or account settings.
The system logs show this:
systemd[1]: Starting PackageKit Daemon...
PackageKit[21372]: daemon start
dbus[1065]: [system] Successfully activated service 'org.freedesktop.PackageKit'
systemd[1]: Started PackageKit Daemon.
PackageKit[21372]: daemon quit
packagekitd[21372]: (packagekitd:21372): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
No idea why, it just randomly started happening a week or two ago. I can update via yast and I assume zypper works as well but the desktop app is broken.
On 07/25/2016 08:56 PM, dilireus wrote:
>
> nrickert;2786497 Wrote:
>> Have you rebooted since the last updates?
>>
>> Authentication depends on “systemd”. Some updates restart “systemd”,
>> and this can break communication with user software.
>
> Many many times. This has been going on for a couple of weeks. I
> reboot every day.
>
>
I run “zypper ps” after every dup in TW and if any process is owned by
root, I reboot, if not I simply logout/login to refresh the processes.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Thanks I never knew I could turn off the app. The sound it makes when it fails to update is atrocious and gives me a shock. KDE really need to work on some more pleasing system sounds.
max@maxlaptop:~> grep systemd /etc/pam.d/*
/etc/pam.d/common-session:session optional pam_systemd.so
/etc/pam.d/common-session.pam-config-backup:session optional pam_systemd.so
/etc/pam.d/common-session-pc:session optional pam_systemd.so
/etc/pam.d/systemd-user:# Used by systemd when launching systemd user instances.
max@maxlaptop:~>
Okay. That’s the correct output. So the pam configuration is not the cause of the problem.
And, yes, you can turn off the updater. My normal practice is use Yast online update, followed by “zypper up”. I usually do this just before I reboot. Most updates can wait a day or two, until I’m ready to boot anyway.
Do you use auto-login? I’m wondering if maybe some process isn’t started when you do that. If you do use auto-login, then perhaps a good test would be to logout (but do not reboot), and then login again to see if updates now work.
I’m having exactly the same problem, but with an added twist. After the error, if I go into Yast’s online update, it starts normally, shows the package manager loading, and shows the repositories being downloaded and refreshed. When the actual app opens and I go to the Package Groups tabs and look at All Packages, it shows that the filesystem, glibc, glibc-extra, libpcre1 and libselinux1 are going to be auto-installed with glibc, glibc-extra and libselinux repeated several times in the list. It also shows that the system has no other packages installed. If I close it and restart, it starts normally again, but this time, the installed package list is correct and there are no odd autoupdates. So it appears that software updates is corrupting the installed package list or something else when it tries to start. This is repeatable - if software update runs, Yast’s online updates opens incorrectly every time afterward.
And it’s even more strange anyway:
If PackageKit would somehow block the package management, YaST should not even start but give an error message.
If PackageKit would corrupt something, it would continue to stay corrupted, and YaST shouldn’t work correctly ever after.
To the others:
check that the package “polkit-kde-authentication-agent-5” is installed, and the process is running.
Either with the system monitor (Ctrl+ESC) or:
ps ux|grep polkit
(run as user)
Also, do you have other polkit related problems, like mounting an external USB drive/stick or problems with sound?
