If I close pamac and open it again using the system-tray icon, I get the same delay.
I can totally work around the delay, so I would not expect it to exist in the first place.
Checking for updates will of course take time, but deselecting one should be instant?
The starter invokes pamac-manager
The system tray icon does pamac-manager --updates
Running both from command line, the first works fine, the other reproduces the problem.
This seems to be a Wayland issue.
Can someone please try to reproduce this?
With --updates the system explicitly checks for updates first, which blocks the process when changing tabs, since the “Installed” or “Browse” tab is only loaded/executed when you click on it and not before. This is why it gets stuck because the database is updated first, and then the installed packages are displayed. So the order matters here due to the big database and because it doesn’t run in parallel. So normally a frontend dev would block switching tabs here, so gray them out for example.
Why not?
The update strategy has to be recalculated again -
you deselected a package that would have been included in the update,
but you opted to not to include one or more packages in the update,
to hold it back …
Incomplete updates will eventually lead to a broken system …