I've recently ran into a problem updating via Discover, I had put off updating for a few months (I had a separate issue regarding flatpak updates) and on reboot I noticed that there were more updates to install. After a few reboots I noticed that the number of packages to update stayed the same. I thought this was odd so I ran the updates via Muon instead. Muon returned the error "libglib2.0-0 3.8015:dependency problems - leaving triggers unprocessed", this was solved by running: sudo dpkg --configure -a sudo apt --fix-broken install After running this code I updated via Dolphin, restarted and the packages to update showed 0. It seems that Dolphin is not showing the above error and it 'looks' like Dolphin is updating but on reboot the number of packages to update stays the same. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.5.0-45-generic (64-bit) Graphics Platform: X11
Does pkcon report the error?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
(In reply to Harald Sitter from comment #1) > Does pkcon report the error? I never used pkcon during the process of fixing the update. What should I run if I encounter this again? I've ran into other issues with Discover not updating properly (denying updating because of certain programs).