Lubuntu 24.04 to 26.04 upgrade didn't upgrade LXQt version

After upgrading from 24.04 LTS to 26.04 LTS, LXQt still shows its version as 1.40. What else needs to be done to upgrade LXQt to 2.30?

1 Like

I’ll be moving your post to the Support and Help area.

I’ll also suggest you provide some pastes giving details, eg.

lsb_release -a; lxqt-about --version

The release-upgrade from 24.04 to 26.04 isn’t yet open, so how exactly did you perform the release-upgrade.

There is a known issue (read about it here) where the update is being offered too early (it’s been offered because 25.10 to 26.04 was open, but shouldn’t have been seen by users of 24.04). I wonder if you saw & tried to accept that, thus you’re still on Lubuntu 24.04 LTS.

3 Likes

You were quite right – looks like I’m still on 24.04 LTS, even though 26.04 was offered in the Update app, and appeared to have installed.

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04
Codename: noble
lxqt-about 1.4.0
liblxqt 1.4.0
Qt 5.15.13

Is there documentation on going from 24.04 LTS → 26.04 LTS? Google is failing me on this one.

Thanks!

1 Like

Lubuntu’s documentation can be found in our manual; for that page on the 26.04 LTS manual that is found by reading

https://manual.lubuntu.me/stable/D/upgrading.html

Please note that link is current for now, as the LTS manual for Lubuntu still shows the 24.04 page, but that will change after Lubuntu 26.10 is released (where the lts in the link will be used to read the 26.04 manual, and stable will show our latest Lubuntu 26.10 manual).

Of course; before upgrading any system, I’d start with reading the

  • Lubuntu 26.04 LTS Release notes where you’d posted originally actually will do
  • Ubuntu 26.04 LTS Release Notes which cover your base Ubuntu system, have links to upgrade notes and more (do note: they’ll concentrate on Server or Desktop (GNOME) changes which won’t impact us flavor users, but the flavor release notes don’t repeat the common parts of which there are many)

I’d also boot a live system and use the ā€œTry Lubuntuā€ mode to see how it performs on your hardware, as if you’re 24.04 LTS install is using the GA kernel stack (6.8) you’ve got a far newer kernel, though if your 24.04 LTS install uses HWE (now 7.0) there is no change there (for now anyway).

6 Likes

Thanks all for the advice.

I tried upgrading via:

sudo do-release-upgrade -d

But the upgrade failed, and referenced /var/log/dist-upgrade/apt.log and main.log.

I’m not seeing a good place to upload those files, here. If anyone wants those and has a place to attach the entire logs, please let me know.

However, here is where things appear to have gone wrong in apt.log:

Investigating (0) qtwayland5:amd64 < 5.15.13-1 → 5.15.18-1 @ii umU Ib >
Broken qtwayland5:amd64 Depends on libxcomposite1:amd64 < 1:0.4.5-1build3 | 1:0.4.6-1build1 @ii umH > (>= 1:0.4.6)
Considering libxcomposite1:amd64 66 as a solution to qtwayland5:amd64 117
MarkKeep qtwayland5:amd64 < 5.15.13-1 → 5.15.18-1 @ii umU Ib > FU=0
Re-Instated libxcomposite1:amd64
Re-Instated qtwayland5:amd64

A lot more library errors follow this, but this is where it began.

And, here is where things appear to have gone wrong in main.log:

2026-07-17 14:23:25,452 DEBUG Foreign (before rewriting sources):
2026-07-17 14:23:25,452 DEBUG Foreign (after rewriting sources):
2026-07-17 14:23:25,453 DEBUG running Quirks.PreDistUpgradeCache
2026-07-17 14:23:25,478 DEBUG none of the ā€˜[ā€˜ubuntu-desktop’, ā€˜kubuntu-desktop’, ā€˜xubuntu-core’, ā€˜xubuntu-desktop’, ā€˜ubuntustudio-desktop’, ā€˜ubuntustudio-desktop-core’, ā€˜lubuntu-desktop’, ā€˜ubuntu-gnome-desktop’, ā€˜ubuntu-mate-core’, ā€˜ubuntu-mate-desktop’, ā€˜ubuntukylin-desktop’, ā€˜ubuntu-budgie-desktop’, ā€˜ubuntu-unity-desktop’]’ meta-pkgs installed
2026-07-17 14:23:25,478 DEBUG guessing ā€˜lubuntu-desktop’ as missing meta-pkg
2026-07-17 14:23:25,807 DEBUG marked_install: ā€˜lubuntu-desktop’ → ā€˜True’
2026-07-17 14:23:26,137 ERROR Dist-upgrade failed: ā€˜E:Unable to correct problems, you have held broken packages.’
2026-07-17 14:23:26,145 DEBUG abort called

Any ideas? Thanks again!

Pausing for Staff Review.

The quality of volunteer help in this topic seems poor.

  • Commands not explained
  • Destructive commands suggested (-d yet again)
  • Volunteers not following up when their suggestion causes problems (responsibility)
  • Obvious diagnostic questions not asked
  • Referrals to offsite ā€œdocumentationā€ of dubious quality

Staff review completed.

Greeting from the Moderators.

Bad, misleading, or barely-relevant advice from multiple users has been removed.

The correct answer for the Support and Help category was to agree with @guiverc…

…and to encourage @ltwally to wait until the supported upgrade path to 26.04 is turned on in a few weeks.

Following bad advice has now caused a problem that @ltwally didn’t previously have.
The general commentary hasn’t helped.
The staff here is a bit annoyed.

Moving forward,

  1. Help @ltwally diagnose the scale of the problem. This is an important step. Don’t shortcut it.
  2. After diagnosis, clearly explain how to fix it. Step by step. Command by command.
  3. DO NOT offer unsupported or dangerous commands under any circumstances. People get banned for that.
  4. Let’s please avoid tangential explanations or comments. If your post does not seek diagnostic information or offer specific help based on a diagnosis, the topic can probably live without it.

Reopening…

4 Likes