Created attachment 160130 [details] 91 Packages, never install Hi Everyone, I am using a computer, Linux OS with the following specs- Using Unstable KDE right now. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Kernel Version: 5.19.0-46-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 13.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS Issue- The Discover, update center and its tiny notification icon at the very bottom right hand side- tells me that there are about 91 updates pending for install. Its so sad that I am still on QT 6 and still KDE 5.7 version, I thought this Unstable version will come with KDE 6 to try :) but no biggie- Im really enjoying this OS- and I love KDE so much, the best Linux. Can someone please help me to run these updates and install. Let me konw if I need to share any log or additional info - im too new at Linux
Are you saying that clicking the "Update All" button as shown in your screenshot does not update the system? if so, I noticed the same problem on Neon Unstable. If you want to update, you can go into the terminal (Konsole) and run these two commands: sudo apt update sudo pkcon update Please keep this bug report open even if the commands above fix your issue, that way a developer can investigate the problem. Plasma 5.27.80 is the development version for Plasma 6, it's a work in progress and as such will contain lots of problems, but it's technically Plasma 6 even though it says 5.27.80. It's recommended to stick to KDE Neon User Edition with Plasma 5.27 for a stable experience until the final version of Plasma 6 gets released. If you'd like to get support from other users and engage with the community, try going to https://discuss.kde.org
Today I was able to confirm clicking on "Update all" doesn't do anything in Discover running on a virtual machine with KDE Neon Unstable.
*** This bug has been marked as a duplicate of bug 470613 ***
Not actually a duplicate of Bug 470613. Can still reproduce it even after I apply the local workaround needed to fix Bug 470613 until the Fedora packagers address the bug downstream.
*** Bug 475377 has been marked as a duplicate of this bug. ***
This has been fixed for me as of today's git master.