SUMMARY When I open Discover, it automatically starts looking for updates and hangs indefinitely. I found a temporary work around. I renamed /usr/lib/qt/plugins/discover/flatpak-backend.so to something else (flatpak-backend.so.bak) so that the file is not recognized by Discover. The problem with that solution, if my understanding is correct, is that Discover will not be able to find updates for Flatpaks. This bug does NOT occur on my Neon system, which also is updated to version 5.26.0. STEPS TO REPRODUCE 1. Open Discover. OBSERVED RESULT Discover hangs indefinitely looking for updates. EXPECTED RESULT Discover will either find updates or not, and indicate whether updates are available. SOFTWARE/OS VERSIONS OS: Arch Linux x86_64 Kernel: 6.0.1-arch1-1 (64-bit) Linux/KDE Plasma: KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Graphics Platform: X11 ADDITIONAL INFORMATION This bug may or may not be related to the bug in bug report 460405 I just filed. After I implemented the temporary solution of renaming flatpak-backend.so to flatpak-backend.so.bak, Discover now indicates whether updates are available or the packages (other than flatpaks) are up to date. However, the Discover Notifier in the system tray now always indicates that updates are available, even if within Discover "Up to date" is indicated.
Sounds like there's an issue in the Flatpak backend. Are you 100% sure that the flatpak backend plugin got upgraded along with everything else?
(In reply to Nate Graham from comment #1) > Sounds like there's an issue in the Flatpak backend. Are you 100% sure that > the flatpak backend plugin got upgraded along with everything else? I have updated Arch multiple times since the issue first popped up (sudo pacman -Syu). I also tried the following: 1.sudo pacman -Rns flatpak
(In reply to Terry Forsythe from comment #2) > (In reply to Nate Graham from comment #1) > > Sounds like there's an issue in the Flatpak backend. Are you 100% sure that > > the flatpak backend plugin got upgraded along with everything else? > > I have updated Arch multiple times since the issue first popped up (sudo > pacman -Syu). > > I also tried the following: > > 1.sudo pacman -Rns flatpak (In reply to Nate Graham from comment #1) > Sounds like there's an issue in the Flatpak backend. Are you 100% sure that > the flatpak backend plugin got upgraded along with everything else? Ignore my previous comment. I accidentally posted it while still typing. I have updated Arch multiple times since the issue first popped up (sudo pacman -Syu). I also tried the following: 1. sudo pacman -Rns flatpak 2. reboot 3. sudo pacman -S flatpak 4. flatpak update It did not regenerate the flatpak-backend.so file. When I rename the flatpak-backend.so.bak to flatpak-backend.so, the problem still occurs.
Reinstall flatpak and running flatpak update did fix the other bug 460405 I reported, however.
Thanks for the info.
The bug just popped up on my Neon system after a recent update. I'm not sure whether it was today's update, but I assume it was. Here is a list updates listed in /var/log/dpkg.log for today: 2022-10-21 03:46:26 startup archives unpack 2022-10-21 03:46:26 upgrade firefox:amd64 106.0+build1-0ubuntu0.20.04.1 106.0.1+build1-0ubuntu0.20.04.1~mt1 2022-10-21 03:46:26 status half-configured firefox:amd64 106.0+build1-0ubuntu0.20.04.1 2022-10-21 03:46:26 status unpacked firefox:amd64 106.0+build1-0ubuntu0.20.04.1 2022-10-21 03:46:26 status half-installed firefox:amd64 106.0+build1-0ubuntu0.20.04.1 2022-10-21 03:46:32 status triggers-pending desktop-file-utils:amd64 0.24-1ubuntu3 2022-10-21 03:46:32 status triggers-pending mime-support:all 3.64ubuntu1 2022-10-21 03:46:32 status triggers-pending hicolor-icon-theme:all 0.17-2 2022-10-21 03:46:32 status triggers-pending man-db:amd64 2.9.1-1 2022-10-21 03:46:32 status unpacked firefox:amd64 106.0.1+build1-0ubuntu0.20.04.1~mt1 2022-10-21 03:46:32 startup packages configure 2022-10-21 03:46:32 configure firefox:amd64 106.0.1+build1-0ubuntu0.20.04.1~mt1 <none> 2022-10-21 03:46:32 status unpacked firefox:amd64 106.0.1+build1-0ubuntu0.20.04.1~mt1 2022-10-21 03:46:32 status half-configured firefox:amd64 106.0.1+build1-0ubuntu0.20.04.1~mt1 2022-10-21 03:46:32 status installed firefox:amd64 106.0.1+build1-0ubuntu0.20.04.1~mt1 2022-10-21 03:46:32 trigproc desktop-file-utils:amd64 0.24-1ubuntu3 <none> 2022-10-21 03:46:32 status half-configured desktop-file-utils:amd64 0.24-1ubuntu3 2022-10-21 03:46:32 status installed desktop-file-utils:amd64 0.24-1ubuntu3 2022-10-21 03:46:32 trigproc mime-support:all 3.64ubuntu1 <none> 2022-10-21 03:46:32 status half-configured mime-support:all 3.64ubuntu1 2022-10-21 03:46:32 status installed mime-support:all 3.64ubuntu1 2022-10-21 03:46:32 trigproc hicolor-icon-theme:all 0.17-2 <none> 2022-10-21 03:46:32 status half-configured hicolor-icon-theme:all 0.17-2 2022-10-21 03:46:32 status installed hicolor-icon-theme:all 0.17-2 2022-10-21 03:46:32 trigproc man-db:amd64 2.9.1-1 <none> 2022-10-21 03:46:32 status half-configured man-db:amd64 2.9.1-1 2022-10-21 03:46:32 status installed man-db:amd64 2.9.1-1
Problem solved. For Neon, the problem went away after another update. For Arch, I uninstalled discover, then reinstalled it. That seems to have cured the issue.
Sounds like packaging/update issues. Thanks for checking in about this!