openSuse 15.2: What is the intended way to stop Package kit nagging
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2? This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies". What I mean by nagging: 1. Requests for Admin privileges in KDE to refresh repositories - I do not know how to stop this without breaking anything else. 2. KDE notifications - I disabled those in KDE - so no probs here. The setup is remote multi user (do I need to say that) VNC server with long-ish uptime - typically few weeks until it needs critical updates. Thank you, Tomas
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-) You do not really need to remove all dependencies. Just the main package, and possibly the desktop applets. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Mon, 2021-05-03 at 23:22 +0200, Carlos E. R. wrote:
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-)
Thanks - That's easy - I "sort of" expected that uninstalling nagware will create another chain of trouble.
You do not really need to remove all dependencies. Just the main package, and possibly the desktop applets.
Uninstalling PackageKit dependencies was an attempt for elaborate joke. IT depends on zypper + .... + ....
On 04/05/2021 00.05, TomasK wrote:
On Mon, 2021-05-03 at 23:22 +0200, Carlos E. R. wrote:
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-)
Thanks - That's easy - I "sort of" expected that uninstalling nagware will create another chain of trouble.
Not directly... what I have noticed is that if some application says it needs you to install something else (say, a codec), the automatic way will fail.
You do not really need to remove all dependencies. Just the main package, and possibly the desktop applets.
Uninstalling PackageKit dependencies was an attempt for elaborate joke. IT depends on zypper + .... + ....
Huh? It does? :-o :-? I have package kit uninstalled, I don't remember any trouble. Well, you have to uninstall and lock it, so that it doesn't get automatically reinstalled. I just have these three locked out: PackageKit PackageKit-browser-plugin PackageKit-gtk3-module -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
* Carlos E. R.
On 04/05/2021 00.05, TomasK wrote:
On Mon, 2021-05-03 at 23:22 +0200, Carlos E. R. wrote:
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-)
Thanks - That's easy - I "sort of" expected that uninstalling nagware will create another chain of trouble.
Not directly... what I have noticed is that if some application says it needs you to install something else (say, a codec), the automatic way will fail.
You do not really need to remove all dependencies. Just the main package, and possibly the desktop applets.
Uninstalling PackageKit dependencies was an attempt for elaborate joke. IT depends on zypper + .... + ....
Huh? It does? :-o :-?
I have package kit uninstalled, I don't remember any trouble. Well, you have to uninstall and lock it, so that it doesn't get automatically reinstalled.
I just have these three locked out:
PackageKit PackageKit-browser-plugin PackageKit-gtk3-module
don't understand the need for locking. I have: rpm -qa *packagekit* libpackagekit-glib2-18-1.2.2-10.2.x86_64 libpackagekitqt5-1-1.0.2-1.9.x86_64 and no lock and have not had any unwanted attempts to reinstall. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 04/05/2021 02.59, Patrick Shanahan wrote:
* Carlos E. R. <> [05-03-21 20:23]:
On 04/05/2021 00.05, TomasK wrote:
I have package kit uninstalled, I don't remember any trouble. Well, you have to uninstall and lock it, so that it doesn't get automatically reinstalled.
I just have these three locked out:
PackageKit PackageKit-browser-plugin PackageKit-gtk3-module
don't understand the need for locking. I have: rpm -qa *packagekit* libpackagekit-glib2-18-1.2.2-10.2.x86_64 libpackagekitqt5-1-1.0.2-1.9.x86_64
and no lock and have not had any unwanted attempts to reinstall.
Maybe you have "no recommends". Anyway, I did the lock operation long ago, it is possible that now it is not needed. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
* Carlos E. R.
On 04/05/2021 02.59, Patrick Shanahan wrote:
* Carlos E. R. <> [05-03-21 20:23]:
On 04/05/2021 00.05, TomasK wrote:
I have package kit uninstalled, I don't remember any trouble. Well, you have to uninstall and lock it, so that it doesn't get automatically reinstalled.
I just have these three locked out:
PackageKit PackageKit-browser-plugin PackageKit-gtk3-module
don't understand the need for locking. I have: rpm -qa *packagekit* libpackagekit-glib2-18-1.2.2-10.2.x86_64 libpackagekitqt5-1-1.0.2-1.9.x86_64
and no lock and have not had any unwanted attempts to reinstall.
Maybe you have "no recommends".
Anyway, I did the lock operation long ago, it is possible that now it is not needed.
I do have "no recommends". I have not yet found an instance reletave to my need where the recommended packages were desired. and I do check, occasionally. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 5/4/21 7:35 AM, TomasK wrote:
On Mon, 2021-05-03 at 23:22 +0200, Carlos E. R. wrote:
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-)
Thanks - That's easy - I "sort of" expected that uninstalling nagware will create another chain of trouble.
You do not really need to remove all dependencies. Just the main package, and possibly the desktop applets.
Uninstalling PackageKit dependencies was an attempt for elaborate joke. IT depends on zypper + .... + ....
I guess a simpler way would be disabling the service systemctl stop packagekit systemctl disable packagekit And then hope that the kde applet doesn't complain too much if the service isn't running. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Tue, 2021-05-04 at 10:00 +0930, Simon Lees wrote:
On 5/4/21 7:35 AM, TomasK wrote:
On Mon, 2021-05-03 at 23:22 +0200, Carlos E. R. wrote:
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-)
Thanks - That's easy - I "sort of" expected that uninstalling nagware will create another chain of trouble.
You do not really need to remove all dependencies. Just the main package, and possibly the desktop applets.
Uninstalling PackageKit dependencies was an attempt for elaborate joke. IT depends on zypper + .... + ....
I guess a simpler way would be disabling the service
systemctl stop packagekit systemctl disable packagekit
And then hope that the kde applet doesn't complain too much if the service isn't running.
Thanks for the suggestion Simon - I did not want to list all the previous attempts I made before uninstalling PackageKit. Disabling the service was the first idea I tried - not very successfully - there seems to be something else running it. This is my systemd command/response log: ~> sudo systemctl status packagekit ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: inactive (dead) May 03 16:10:12 nuc58 PackageKit[15566]: daemon start May 03 16:10:12 nuc58 systemd[1]: Started PackageKit Daemon. May 03 16:10:12 nuc58 PackageKit[15566]: uid 1026 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) May 03 16:15:18 nuc58 PackageKit[15566]: daemon quit May 03 17:10:12 nuc58 systemd[1]: Starting PackageKit Daemon... May 03 17:10:12 nuc58 PackageKit[16387]: daemon start May 03 17:10:12 nuc58 systemd[1]: Started PackageKit Daemon. May 03 17:10:12 nuc58 PackageKit[16387]: uid 1026 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) May 03 17:10:16 nuc58 PackageKit[16387]: uid 1026 failed to obtain auth May 03 17:10:33 nuc58 PackageKit[16387]: daemon quit ~> sudo systemctl stop packagekit ~> sudo systemctl status packagekit ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: inactive (dead) May 03 16:10:12 nuc58 PackageKit[15566]: daemon start May 03 16:10:12 nuc58 systemd[1]: Started PackageKit Daemon. May 03 16:10:12 nuc58 PackageKit[15566]: uid 1026 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) May 03 16:15:18 nuc58 PackageKit[15566]: daemon quit May 03 17:10:12 nuc58 systemd[1]: Starting PackageKit Daemon... May 03 17:10:12 nuc58 PackageKit[16387]: daemon start May 03 17:10:12 nuc58 systemd[1]: Started PackageKit Daemon. May 03 17:10:12 nuc58 PackageKit[16387]: uid 1026 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) May 03 17:10:16 nuc58 PackageKit[16387]: uid 1026 failed to obtain auth May 03 17:10:33 nuc58 PackageKit[16387]: daemon quit ~> sudo systemctl disable packagekit ~> sudo systemctl status packagekit ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: inactive (dead) May 03 16:10:12 nuc58 PackageKit[15566]: daemon start May 03 16:10:12 nuc58 systemd[1]: Started PackageKit Daemon. May 03 16:10:12 nuc58 PackageKit[15566]: uid 1026 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) May 03 16:15:18 nuc58 PackageKit[15566]: daemon quit May 03 17:10:12 nuc58 systemd[1]: Starting PackageKit Daemon... May 03 17:10:12 nuc58 PackageKit[16387]: daemon start May 03 17:10:12 nuc58 systemd[1]: Started PackageKit Daemon. May 03 17:10:12 nuc58 PackageKit[16387]: uid 1026 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) May 03 17:10:16 nuc58 PackageKit[16387]: uid 1026 failed to obtain auth May 03 17:10:33 nuc58 PackageKit[16387]: daemon quit ~> sudo systemctl status packagekit-background.service ● packagekit-background.service - Script to update the system with PackageKit Loaded: loaded (/usr/lib/systemd/system/packagekit- background.service; static; vendor preset: disabled) Active: inactive (dead) ~> sudo systemctl status packagekit-background.timer ● packagekit-background.timer - Systemd timer to update the system daily with PackageKit Loaded: loaded (/usr/lib/systemd/system/packagekit-background.timer; disabled; vendor preset: disabled) Active: inactive (dead) Trigger: n/a Root Crontab is empty. There is no /etc/sysconfig/packagekit either There is no packagekit process running either. - Yet it comes alive every now and again with kdesu asking for root credentials. I am kind of curious why leap 15.1 did not behave this annoying way - not that I miss it. I setup and configure computers with Ansible, so I am pretty sure that I did nothing special to deal with PackageKit for 15.1. Anyway, I have uninstalled it - hope that is the end of my trouble. Thanks for replies, Tomas PS: For curious minds. I see similar PackageKit nagging on laptops - it seems to starts after they come out of suspend.
On 04.05.2021 03:30, Simon Lees wrote:
On 5/4/21 7:35 AM, TomasK wrote:
On Mon, 2021-05-03 at 23:22 +0200, Carlos E. R. wrote:
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-)
I am very amused by this town legend about evil PackageKit that goes on and on for years ...
Thanks - That's easy - I "sort of" expected that uninstalling nagware will create another chain of trouble.
You do not really need to remove all dependencies. Just the main package, and possibly the desktop applets.
Uninstalling PackageKit dependencies was an attempt for elaborate joke. IT depends on zypper + .... + ....
I guess a simpler way would be disabling the service
systemctl stop packagekit
PackageKit daemon exits after several minutes of inactivity so most of the time this service is not active anyway.
systemctl disable packagekit
PackageKit daemon is started by D-Bus on request so this does absolutely nothing.
And then hope that the kde applet doesn't complain too much if the service isn't running.
PackageKit is a tool that works on request of other, user facing, applications. So instead of smashing around with big hammer all that is needed is disabling auto-start of applications that use PackageKit. This is gnome-software in GNOME (even on Leap, although it invokes different program to perform actual installation), it is package-update-indicator in default Xfce install, and Software Update plasmoid in KDE. In all cases it is rather simple to disable auto-start of corresponding component. In case of KDE it also leaves you without any UI to trigger update manually, so uninstalling and locking plasma5-pk-update is probably easier. That said, I'm using PK based update on all VMs, both Leap and TW, KDE, GNOME and Xfce, and so far I had not much issues with *PackageKit*. Most problems were in user facing components, Gnome Software mostly, but it looks good in GNOME 40 (at least all issues I had are gone). One case when gnome-software fails is EULA. Upstream refuses to add EULA support and I think there was SUSE patch but may be I'm mistaken. Fortunately, current g-s fails right away. Now when I mention it I have never seen EULA in KDE, which opens up interesting question - is it legal at all to suppress it :)
On Tue, 2021-05-04 at 08:55 +0300, Andrei Borzenkov wrote:
I guess a simpler way would be disabling the service
systemctl stop packagekit
PackageKit daemon exits after several minutes of inactivity so most of the time this service is not active anyway.
systemctl disable packagekit
PackageKit daemon is started by D-Bus on request so this does absolutely nothing.
And then hope that the kde applet doesn't complain too much if the service isn't running.
PackageKit is a tool that works on request of other, user facing, applications. So instead of smashing around with big hammer all that is needed is disabling auto-start of applications that use PackageKit. This is gnome-software in GNOME (even on Leap, although it invokes different program to perform actual installation), it is package-update- indicator in default Xfce install, and Software Update plasmoid in KDE. In all cases it is rather simple to disable auto-start of corresponding component. In case of KDE it also leaves you without any UI to trigger update manually, so uninstalling and locking plasma5-pk-update is probably easier.
That said, I'm using PK based update on all VMs, both Leap and TW, KDE, GNOME and Xfce, and so far I had not much issues with *PackageKit*. Most problems were in user facing components, Gnome Software mostly, but it looks good in GNOME 40 (at least all issues I had are gone).
One case when gnome-software fails is EULA. Upstream refuses to add EULA support and I think there was SUSE patch but may be I'm mistaken. Fortunately, current g-s fails right away. Now when I mention it I have never seen EULA in KDE, which opens up interesting question - is it legal at all to suppress it :)
That is educational, I noticed the Dbus, but did not make the connection - thank you! So, I have re-installed PackageKit back and disabled Software Updates in KDE System tray. Hopefully that will stop the hassle. Tomas
On 04/05/2021 07.55, Andrei Borzenkov wrote:
On 04.05.2021 03:30, Simon Lees wrote:
On 5/4/21 7:35 AM, TomasK wrote:
On Mon, 2021-05-03 at 23:22 +0200, Carlos E. R. wrote:
On 03/05/2021 21.39, TomasK wrote:
What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2?
This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies".
Just uninstall it :-)
I am very amused by this town legend about evil PackageKit that goes on and on for years ...
Not evil... I simply do not want it running :-) For example, I do not want anything using bandwidth in my laptop when it is using the metered connection of my phone. And it has to be something that globally disables it, not per user. I can not afford the risk of it running if I start a different user. I also do not want to install things using it, I want all my package management done by YaST or zypper, where I have all the adjustments at my disposal. ...
PackageKit is a tool that works on request of other, user facing, applications. So instead of smashing around with big hammer all that is needed is disabling auto-start of applications that use PackageKit. This is gnome-software in GNOME (even on Leap, although it invokes different program to perform actual installation), it is package-update-indicator in default Xfce install, and Software Update plasmoid in KDE. In all cases it is rather simple to disable auto-start of corresponding component. In case of KDE it also leaves you without any UI to trigger update manually, so uninstalling and locking plasma5-pk-update is probably easier.
Well, one issue is that the name of the applet changed over the years. Considering I do not want it, rather them, to run for any user at all, at least not automatically, the only way I know is removing all those applets. In the past, it meant removing other things because of dependencies. So, if there were a global, root controlled, easy way to disable the applets globally, in several tunable degrees, we would not use the hammer-maze. Say "do not ever check for updates" and "only these users can do package management". So I try removing the locks. It wants to delete "package-update-indicator" (it was installed). /I/ delete (and will lock) gnome-software I don't know the actual name of the KDE thing. I found: mate-applet-softupd - MATE panel applet for software update notifications plasma5-pk-updates - Software Update Manager for Plasma pk-update-icon - Software Update Notifier based on PackageKit Deleted, will be locked. So, now "zypper ll" has: 2 | PackageKit-browser-plugin | package | (any) 9 | gnome-software | package | (any) 12 | mate-applet-softupd | package | (any) 13 | package-update-indicator | package | (any) 14 | pk-update-icon | package | (any) 15 | plasma5-pk-updates | package | (any) It is five things to remember to lock, on every install... -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Patrick Shanahan -
Simon Lees -
TomasK