Hi all,
Just wondering what is happening with the updates since Plasma 6 came out. I used to get software update notifications on a daily basis, but this hasn’t happened since I upgraded last week.
Is there a new way to check for updates?
TW Snapshots 13, 14, and 15 have been released, each one day-after-day.
(11 was the KDE upgrade).
There’s only one true way to check for updates - at a terminal:
.# zypper -vvvv dup
1 Like
The update notifier applets are no longer compatible with Plasma 6 and had to be removed. Maybe if the devs of this external notifiers adapt them for Plasma 6, they might come back again.
If you have Discover installed, there is discover6-notifier.
1 Like
I am also not receiving updates since plasma6 packages started appearing for x86 but I’m running an aarch64 install in a VM on a M2 Macintosh. What architecture are you using? I do all my package management with zypper.
Core™ i5-6500. As mentioned above, Discover has a section for updates and I am now using that to check for/apply updates.
The update function of Discover seems perpetually broken on my install. Just hangs when checking for updates. I did however start getting updates via zypper after posting here. Booted to SDDM (did not log in), switched to a TTY session, logged in as root and installed the 650 odd updates. Rebooted and logged into a Wayland session with an invisible cursor. In X11 I get a visible cursor, but Firefox and Thunderbird have massive black borders around their windows. Changing cursor theme sets doesn’t help with the Wayland invisible issues. It’s just Linux being Linux.
1 Like
do you have discover6-backend-packagekit installed?
TW has never had “updates”. TW only has full release upgrades, which can happen as many as 8 times in one calendar week! This is why we do zypper dup (aka --dist-upgrade or Distribution Upgrade) instead of zypper up. What could the old notifier actually tell you, except skipping a day or two or three by not appearing because there was no upgrade released for a day or few? Do you interrupt everything else to upgrade the moment the notifier appears? I don’t get it. 
Is it really that hard to understand?
I found the notifier really usefull. After systemstart it told me if there were updates/upgrades available. If the pop-up wasn’t there, there where no updates/upgrades and i didn’t had to apply anything via zypper dup.
Also the periodically check over the day was really usefull…
Opening the terminal to check if updates/upgrades are available is not that convenient like the little pop up that told me, hey there are 130 updates available! Check via console!
And believe it or not, there are more upgrade/update strategies than only yours. And yes, there are experienced ppl around here, that apply patches/security fixes/upgrades/updates as soon as they are available!
And regarding Discover: you love it or you hate it. I hate it and removed this bloat from my machines so the Disvover notifier is no alternative solution for me…
1 Like
That right there is a something that didn’t occur to me. “Do I need to upgrade” is not the first thing on my mind on a daily login, and even if it was I wouldn’t expect repo refresh to happen so fast that any notifier would be ready by the time login completes so as to induce me to log right back out to get upgraded outside running X. My main box is up 24/7. Logging out here is something that typically happens roughly 3-5 times a month, typically to clear cruft from RAM or bring a new kernel up.
My machines get started daily. The repo refresh was done by the notifier (via packagekit backend) directly after the GUI was up. That means seconds after the system was up, i already knew if i had to apply upgrades.
And experiened users can see at the package list, if the upgrade/update can be applied from a running GUI session…The Plasma upgrade was the last one which needed a drop to a CLI session…
I wonder if that could work with Leap? update/leap/15.5/sle habitually seems to take longer to refresh than all other repos combined, in combined total not unusually longer than the time it takes to get from Grub to greeter.
I am having similar problems. After upgrade to plasma 6, I am no longer receiving any updates from zypper. Discover seems to be providing a handful of updates daily.
In the past I would see update notifications in the desktop or via the command line every single day.
It has been four or more days since the lack of updates; which is extremely unusual.
There seems to be a massive missunderstanding. There ARE updates available if you use the right way to upgrade your Tumbleweed via zypper dup. The only missing stuff is the notifier.
The notifier can be installed by
sudo zypper in discover6-notifier
I have it installed already, but I don’t get any notifications for the updates. Is there something else that needs to be done to make it work?
I can’t speak to the UI notifications failing being the only issue for others - but for me - that is not the case. Running zypper refresh and zypper -vvvv dup does not show any updates either.
I get the same results with zypper as I get from yast2 UI. Nadda. Nyet. Nunca. Nine. None. No updates.
NOTE - I have also checked the enabled repositories - and they remain the same as prior to the upgrade.
Normally I do my updates via YaST UI … and that doesn’t show available packages. Hence I went dumpster diving - which led me to here - which led me to check zypper dup - which provides the same nothingness.
@shanegibson So what Tumbleweed snapshot are you on; cat /etc/os-release | grep VERSION_ID
You should not use YaST for TW, only zypper dup
Why should I expect YaST to not work for Tumblweed? It worked perfectly smoothly and without a hitch for quite a long time … until this recent update round.
That is a fairly ridiculous position - in my opinion. I would expect YaST to be able to update the system equally as well as zypper. In effect they should be doing exactly the same things.
Up until a week ago … they were …