-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
22.04 Deferred Improvements #279
Comments
Pretty much sums up the "Pop!_Shop freezes" report everyone makes. Your suggestions are perfect. |
These have to do with new pop-upgrade integration and are not related to existing Pop!_Shop performance complaints. |
At least this one happens all the time for almost everyone. This adds the frozen stage while checking for updates. (Doesn't happen for everyone; i guess depends on internet speed?) |
Yes, it was expected behavior before (the update checks, not the freezing), and that functionality being moved into a different component will have the side effect of removing it from the Pop!_Shop. I did specify "after clicking a notification from system-updater," so I would still expect the Pop!_Shop to check for updates if you start it by clicking on it in the dock/application menu/etc. It might not be entirely necessary for that to be the case, but removing the Pop!_Shop's ability to refresh the package lists would be a separate discussion. That could lead to issues trying to install a package after it's been updated and before system-updater's next update check (which could be as long as a month away, depending on user configuration.) |
This is a list of items that were not addressed in pop-os/system-updater#1 / #225 / pop-os/shop#342, but could be improved. These can be broken out into separate issues if desired, I'm just getting them down first.
to 12apt autoremove
to keep clutter from building up on the systemInstalled
tab when clicking an update notification (it currently opens to theHome
tab if the Pop!_Shop process was already running in the background before clicking the notification)The text was updated successfully, but these errors were encountered: