![]() Registered Member ![]()
|
This worked. Thank you. |
![]() Registered Member ![]()
|
wine32 does not work and can't install now.
|
![]() Registered Member ![]()
|
Yeah, I am aware of this. However, personally I prefer the command line for upgrade operations.
Thanks for the confirmation. |
![]() Registered Member ![]()
|
I'm also getting the "Please install all available updates for your release before upgrading" message and I've tried all of the suggestions in this thread so far to no avail. Anyone have any other ideas to try?
|
![]() Registered Member ![]()
|
I removed all wine32 packages, but the paradox remains the same: no packages need updates, but release-upgrade won't work because of missing updates. ![]() |
![]() Registered Member ![]()
|
I'm not getting the 20.04 upgrade notification. What gives?
|
![]() Registered Member ![]()
|
A small program called "distro-release-notifier". It's icon is residing in KDE's system-tray, and when clicked upon, a small windows opens and tells me that "Upgrade failed with the following output:..."
|
![]() Registered Member ![]()
|
I also had an problem with update to Focal.
After distro updater checked for updates I got an error: "Please install all available updates for your release before upgrading." I solved this problem with Muon package manager. In "Upgradeable" tab I found package libodbc1 and marked it for update. After that package update appeared in Discover and I managed to update KDE Neon to Focal without problem. But after update I faced a number of problems: 1. Virt-manager gets stuck trying to connect to QEMU/KVM. But Virt-manager does not freeze. The menu works. I can create a new connection, but with the same result. Virtual Box works fine. 2. the PC does not shut down or restart normally. It gets stuck on KDE Neon logo with animated circle. 3. I tried to log out once and the PC freeze. 4. I'm using fullscreen application launcher. After reboot buttons "Shut down" and "Reboot" disappears from it. But after I temporarily change application launcher, buttons appears again. Please let me know if you know how to troubleshoot these problems. Because I have no ideas. None of these problems cause obvious errors and I don't know where to start. |
![]() Registered Member ![]()
|
I tried the upgrade. It appeared to go smoothly right up until the end where it stated the upgrade failed (lovely).
I rebooted, found I had the GRUB bootloader issue present under 18.04 with the latest GRUB 2 security update. Repaired that and everything appeared fine - Until I tried installing/uninstalling software... Apparently apt couldn't access the keychain to store or even access old secure keys needed to add PPA's, I didn't really have time to check what was going on as I had work to do - So I rolled back using my nightly backup and am now back on 18.04LTS. Has anyone encountered this issue? With KDE basically forcing the change by July, I'd like to be able to upgrade without hosing my install as opposed to performing a full wipe and reinstall of the OS. |
![]() Registered Member ![]()
|
I'm a little bit concerned about this upgrade, and would wait until I'm sure on what to do in case of problem.
I have never been noticed about new upgrade, even if I have always followed all updates. From Terminal I get: "No packages require updating to newer versions." Still on KDE neon 5.19 Just a question: what is the difference between using apt and pkcon, for this upgrading ? |
![]() Registered Member ![]()
|
2. Was fixed with BIOS update 4. Fixed by itself. |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell