Discover notifier always shows updates available

Hi,
Discover notifier shows that updates are available all the time, even after I installed the latest ones. Any clue how to fix this?

Can you share some details about your operating system? What OS, what version, what version of Plasma, etc?

Running kinfo usually provides most or all of the needed information.

Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-41-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics

Discover 6.1.2

Can you share a screenshot of your Discover updates screen?

There you go!

So, I’m confused - what is showing you have updates?

Yeah, that is clearly a bug.

Might be a debian thing, because something similar happens in webmin that I run on a debian based distro.

Is it persistent even after a logout/login or a reboot?

@guss77 The discover notifier in the taskbar is showing that updates are available.
@bedan Yes this is persistent after relog and reboots.

You are not alone. This has been broken for me since 5.27.6 or so and has persisted through to 6.1.2. It was also broken for a while back in 5.24 but went away only to come back. I have posted about it a couple of times with no solution. I was actually about to post it again as it bugging the hell out of me, but here you are. All I can do is force it to hide and just let the regular notifications do it thing. As it seems to be an issue with both Xorg and Wayland, and with my user account and a new account, I am assuming its system wide and not specific to a user account or WM settings.

1 Like

A while ago I found a forum post of someone with a similar issue and the recommendation was to make sure the user was in the wheel group and wheel had sudo rights, but it was an Arch Linux forum so I was hesitant to try it. I don’t even have a wheel group. Does that ring a bell for anyone?

I also found bug report 438670 with the exact same thing. I checked the current code to see if the line that fixed it is still present but the entire structure of the file changed. Maybe I’ll submit a new bug report.