Summary: | After cancelled upgrade I don't know how to restart the upgrade | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | Jonas Eberle <flightvision> |
Component: | general | Assignee: | Neon Bugs <neon-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | jr, neon-bugs, sitter, tynach2 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jonas Eberle
2020-08-12 11:26:25 UTC
For me, logging out and back in gives the notification again. I've been trying to figure out what packages are causing a bunch of KDE packages to just be marked for removal instead of upgrading, and for a while I had to constantly log in and out to test different package removals/installs. Eventually I got fed up with it and filtered ksysguard by the word 'upgr' when running the upgrader, and found out this is the full command: do-release-upgrade -m desktop -f DistUpgradeViewKDE If you just want to do it over the command line, you can leave out the '-f DistUpgradeViewKDE' part; but if you want the GUI to pop up, leave it in. Thank you very much Colin, That's exactly the information I missed on https://community.kde.org/Neon/FocalUpgrades as for me logging in/out doesn't bring up the notification again. - do you know who I could talk to to suggest including it there? On that note (but another topic) it might also be important to have better public information about what `pkcon update` really does. If it is just a wrapper around the OS's update mechanisms without any additional logic it would spread a lot less uncertainty. As package management in neon is suggested to be done with `pkcon`, I didn't want to just start the Ubuntu updater in fear it could do harm. In forums and on reddit people suggest `do-release-upgrade --allow-third-party` but nobody yet seemed to have the original command that KDE runs - thank you! No idea who to talk to, unfortunately. I only know what the command is by using ksysguard, and thankfully not being affected by the bug you're affected by (the notification not popping up each login). |