[RESOLVED] Update failed (to 25.10)

[checco]

When I try to upgrade my Kubuntu 25.04 to 25.10, I get a window that says "Upgrade failed with the following output:" but nothing is written (see screenshot). What can I do?

[Snowhog]

Don't use Discover.

Open Konsole. Type: sudo apt update && sudo apt full-upgrade to ensure that everything is 'up to date'. If any packages are reported as being held (phased), you won't/shouldn't attempt to upgrade to 25.10 yet.

If you aren't told any packages are being held, then type: sudo do-release-upgrade

[checco]

Don't use Discover.

Open Konsole. Type: sudo apt update && sudo apt full-upgrade to ensure that everything is 'up to date'. If any packages are reported as being held (phased), you won't/shouldn't attempt to upgrade to 25.10 yet.

If you aren't told any packages are being held, then type: sudo do-release-upgrade

Two packages appear to be upgradable, even though everything is up to date on discover. With sudo apt full-upgrade it tells me "Not yet updated due to staggering:
fwupd libfwupd3" How can I update them?

[Snowhog]

You can bypass the phasing hold on these two packages by running sudo apt -o APT::Get::Always-Include-Phased-Updates=true install fwupd libfwupd3 If the packages update without any issue (no ERRORS), you can run the sudo do-release-upgrade command.

[checco]

You can bypass the phasing hold on these two packages by running sudo apt -o APT::Get::Always-Include-Phased-Updates=true install fwupd libfwupd3 If the packages update without any issue (no ERRORS), you can run the sudo do-release-upgrade command.

Everything seems to have gone well, the packages are up to date. Tomorrow I'll try to launch the upgrade with the command 'sudo do-release-upgrade'. I'll let you know...for now, thanks.

[TheSupremeVizier]

I have experienced the same problem. The output of
sudo apt full-upgrade
shows me that
fwupd libfwupd3
are not upgrading yet due to phasing.
When I try
sudo apt -o APT::Get::Always-Include-Phased-Updates=true install fwupd libfwupd3
the output states
Error: Unable to locate package libfwupd3

It seems like "fwupd libfwupd3" have been phase-delayed for a very long time compared to other previous phasing delays.
Should I continue to wait on this? Or is this a problem with my system not performing correctly?

My nearly daily update regimen is:
sudo apt update
sudo apt list --upgradable
sudo apt full-upgrade
sudo apt autoremove


Here is the most recent operation and output of that regimen:
<user>@<hostname>~$ sudo apt update
[sudo] password for <user>:
Hit:1 http://us.archive.ubuntu.com/ubuntu plucky InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu plucky-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu plucky-backports InRelease
Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:5 http://security.ubuntu.com/ubuntu plucky-security InRelease
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Notice: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://dl.google.com/linux/chrome/deb stable InRelease' doesn't support architecture 'i386'
<user>@<hostname>:~$ sudo apt list --upgradable
fwupd/plucky-updates 2.0.13-1~25.04.1 amd64 [upgradable from: 2.0.7-1]
libfwupd3/plucky-updates 2.0.13-1~25.04.1 amd64 [upgradable from: 2.0.7-1]
<user>@<hostname>:~$ sudo apt full-upgrade
Not upgrading yet due to phasing:
fwupd libfwupd3

Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 2
<user>@<hostname>:~$ sudo apt autoremove
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 2

Am I doing something wrong?

[claydoh]

https://bugs.launchpad.net/ubuntu/+s...r/+bug/2130246

[claydoh]

https://discourse.ubuntu.com/t/ubunt...to-25-10/71295

[TheSupremeVizier]

Thanks, claydoh.
It's late and my eyes are dying on me, so I thought I'd write this before heading to bed.
Looking at your most recent link, I see there is a command do-release-upgrade -f DistUpgradeViewKDE that is being suggested.
I had tried a similar command earlier using the "-m" argument and the output claimed to not support that argument even though the man page claimed it was valid.
For now I will assume that the "-f" switch will work.
I hope to perform this task tomorrow.

[checco]

Successful update to 25.10. Thanks to Snowhog for their contribution.

[claydoh]

I had tried a similar command earlier using the "-m" argument and the output claimed to not support that argument even though the man page claimed it was valid.

Yes, it seems Ubuntu removed the -m option at some point, which is what caused this bug in the applet, as it was coded to use it.

Which main page did you see the "m"? So we can get them to edit it if necessary.

https://help.ubuntu.com/community/Qu...grades/Kubuntu

[TheSupremeVizier]

The man page is titled "DO-RELEASE-UPGRADE(8)" on 25.04.

[TheSupremeVizier]

EDITED TO MODIFY/REMOVE ITEM 5 BELOW. I just awoke the system from sleep and it responded very quickly. Perhaps something to do with caching to/from SSD/RAM.

Update completed. I see that we only have Wayland now. There are issues very similar to what was found with Wayland before in 25.04. Stuff like:
1. emacs windows are difficult to resize. Not an issue with X11.
2. multiple tabs in Konsole are not saved between login sessions. Not an issue with X11.
3. browser and Konsole positions are not saved between login sessions. Not an issue with X11.
4. multiple Konsole windows are not saved between login sessions...only one Konsole window is saved. Not an issue with X11.
xxx Item 5 is no longer valid.
5. waking from sleep mode is ridiculously glacial...I am talking at least five minutes or more... Not an issue with X11.
xxx Ignore Item 5.

One possibility for the slow waking from sleep mode may be an issue between 25.10 and the proprietary Nvidia (GeForce RTX 5070) driver version 580.95.05. I went to the Nvidia site and this is their most recent driver. As such, I will shutdown instead of using sleep mode. Yes, this is a PITA, but shutdown is better than not going into sleep mode and constantly burning 200 Watts when idle.

Since I have previously mentioned these issues here, I don't see the need to open new individual posts for these issues.

[jlittle]

Update completed. I see that we only have Wayland now.

I've got it back by running

sudo apt-get install plasma-session-x11

and a restart (logging out wasn't enough).

That was annoying. Some of my stuff doesn't work with Wayland, like running konsole and my mouse mappings, things I use all the time.

[Snowhog]

Some of my stuff doesn't work with Wayland,

Yeah. Synaptic Package Manager. I'm guessing that any GTK-based application will have issues running on Wayland.