Bug 432154 - updates are done, though beeing deselected
Summary: updates are done, though beeing deselected
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: PK Updates widget (show other bugs)
Version: 6.2.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Jan Grulich
URL:
Keywords:
: 469185 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-01-26 12:14 UTC by Peter Möller
Modified: 2025-01-16 17:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Möller 2021-01-26 12:14:15 UTC
SUMMARY
Its hard to do the right infos, here some explanations ahead:
- The addressed tool is called "Softwareaktualisierung" in German language and settled in the taskbar. 
- Because of a broken amd graphics kernel module in kernel *,60.1 I'm working with kernel-default *.57 and also have uninstalled the *.60 kernel with YaST.
- I heaviliy try to avoid the *,60 kernel, because display is destroyed then 

STEPS TO REPRODUCE
1. If updates are recommended, activate the software updater
2. Of course, the update to kernel *.60 will be part of the updates
3. Deselect to update to kernel *.60 and activate the updates

OBSERVED RESULT
Twice I had the situation, that the *.60 kernel still gets installed


EXPECTED RESULT
suppress update to kernel *.60 or at least note it as implicating

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: - openSUSE 15.2
(available in About System)
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.71.0
Qt Version: 4.12.7

ADDITIONAL INFORMATION
This one is none of my best reports, just ask, if there is more info needed ;-).
Yesterday updates had 4 components, where it happened. But I don't know how to find it out afterwards.
Its just for me pretty nasty, because with a broken screen it is work to get rid of the *.60 kernel
Comment 1 Peter Möller 2021-02-09 00:28:23 UTC
I opened a parallel issue for YaST2, where the reasons for this behaviour were found ;-). Maybe, this gives a hint to this problem too:
https://bugzilla.opensuse.org/show_bug.cgi?id=1181622

Not a straight possibility for all of you to reproduce this scenario.
=> Since we reached *63 now, its ok for me to close this one ;-)
Comment 2 TraceyC 2025-01-16 17:27:21 UTC
*** Bug 469185 has been marked as a duplicate of this bug. ***