Hi, i understood that tumbleweed has to be updated via zypper dup so i expected that no automatic update take place. Sometimes during logoff the message “system is updating” appeared.
Is this expected behaviour?
Since last three days zypper dup shows that nothing has to be done, is normal?
Thanks a lot
As far as I know, if you are using Gnome then it does updates in the background (or when rebooting). KDE does not do that. I don’t know about other desktop environments.
Yes, i am using gnome. Is it possibile (and safe) to remove this gnome settings or it is not so important cause zypper dup is recommended and it is a superset of this automatic operation?
We are tryng to use tumbleweed also as development env and we would like to have full control on update operations in order to minimize problems.
Thanks
@Marcodepe Depends on what is being updated… could be user flatpaks as well as packagekit and fwup-refresh.timer.
1 Like
@malcolmlewis i don’t know which flatpaks app gnome have installed by default so i dont know the impact (i will check via flatpak list command), and i dont like so much that these extra sources were configured and used by default installing gnome. What i understood from your response is not to remove the automatic settings. If i understood well via systemctl packagekit is already inactive by default.
@Marcodepe On a test system here I saw an auto update from packagekit…
systemctl status packagekit
○ packagekit.service - PackageKit Daemon
Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
Active: inactive (dead)
Apr 02 09:37:05 waldorf PackageKit[2654]: get-updates transaction /4_adebbddd from uid 1000 finished with success after 3293ms
Apr 02 09:37:05 waldorf PackageKit[2654]: new update-packages transaction /5_adbdcaee scheduled from uid 1000
Apr 02 09:37:06 waldorf packagekitd[2654]: DownloadProgressReportReceiver::start():https://dl.google.com/linux/chrome/rpm/stable/x86_64 --google-chrome-stable;135.0.7049>
Apr 02 09:37:09 waldorf PackageKit[2654]: update-packages transaction /5_adbdcaee from uid 1000 finished with success after 3306ms
Apr 02 09:37:14 waldorf PackageKit[2654]: get-updates transaction /6_cdebeddd from uid 1000 finished with success after 2695ms
Apr 02 09:37:21 waldorf PackageKit[2654]: get-updates transaction /7_dbbaecbe from uid 1000 finished with success after 3143ms
Apr 02 09:37:24 waldorf PackageKit[2654]: get-updates transaction /8_eeceecbd from uid 1000 finished with success after 3158ms
Apr 02 09:37:42 waldorf PackageKit[2654]: daemon quit
Apr 02 09:37:42 waldorf systemd[1]: packagekit.service: Deactivated successfully.
Apr 02 09:37:42 waldorf systemd[1]: packagekit.service: Consumed 31.289s CPU time.
On shutdown I saw the update run, normally I disable the packagekit service and mask… not worried about it’s presence and getting updated to stay current just in case I want to re-enable at some point (I use a system configuration script to set systems up as it works with Leap, Tumbleweed and MicroOS based (via combustion).
if [ $REMOVE_PACKAGEKIT == 1 ]; then
echo "Disable Packagekit services and mask"
systemctl disable --now packagekit-background.service packagekit-offline-update.service \
packagekit-background.timer packagekit.service
systemctl mask packagekit-background.service packagekit-offline-update.service \
packagekit-background.timer packagekit.service
fi
1 Like
@malcolmlewis so with these systemctl commands l could disable all automatic updates and i should update only via zypper dup, correct?
Thanks a lot indeed.
But if you think all this is unnecessary please tell me. I am really newbie of tumbleweed.
@Marcodepe yes, disable and mask, then just zypper dup. Might want to check fwupd services/timers as well.
1 Like