Lubuntu (stonking) 26.10 Beta issue tracker

Flavors & Remixes Lubuntu
1

This is a list of KNOWN issues that exist currently in the Lubuntu 26.10 BETA image.

This post is a WIKI and can be edited so items can be added/removed from this top-index, but please only do so if you’re a Lubuntu team member. Being listed is to allow easier tracking.

If you discover bugs in your testing, PLEASE REPLY to this post with what you discovered, include link to the bug report on launchpad & whatever more you believe will be useful. Team members may add it to this ‘index’ list.

Lubuntu 26.10 Beta Release Notes can be read here.

2 Likes
Lubuntu 26.10 Beta Released
2

Fresh install of Lubuntu stonking 26.10 beta RC, informational label is incorrect

guiverc@dc7700:~$ sudo blkid
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
...
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sda1: LABEL="lubuntu_2604" UUID="2ca8557e-12f3-4ceb-9d03-fcae31de050f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="048639d6-01"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"

/dev/sda1: LABEL=“lubuntu_2604”

The label on the partition says “lubuntu_2604”; if a user of a multiboot install had two systems (26.04 LTS & 26.10) & decided the wanted to keep only LTS release, they both [currently] show same value & thus wrong partition could be erased, if user didn’t check other details.

Noticed by @leok ; thanks for your testing !

26.10_26.04_label
26.10_26.04_label1406×637 59.5 KB

1 Like
Lubuntu 26.10 Beta Released
3

On some setups, with multiple monitors of varying resolutions/proportions, possibly specific graphics hardware too, the TRY/INSTALL dialog isn’t showing

This is a ‘petty’ issue, but could cause someone to wait a long time, as the TRY INSTALL doesn’t show until the user performs an action such as hitting ALTTAB or switch to text terminal, login …

If you encounter this, just hit the keys ALTTAB and it’ll proceed normally & it’ll work perfectly.

This will impact very few users, but we know of at least one box thus far that is impacted by it.

1 Like
4

Some other petty issues that could impact

  • specific monitor arrangements

which trigger old bugs with usage of openbox.

Symptoms can include gaps between monitors (when dragging mouse pointer from one screen to the other) for one, and others.

These aren’t new, and easily resolved by switching WM from openbox to another (such as xfwm4), where issue will be gone; or just using a Wayland session.

You can also change monitor.settings position & the issue won’t happen too (if lucky, or reoccur if unlucky).

Will impact almost no end-users anyway, again needing specific monitor resolutions & setups to happen.

2 Likes
5

apt sometimes has odd behavior when resolving packages, choosing packages that one wouldn’t expect if presented with multiple choices that can satisfy a dependency.

This has not been filed as a bug in Ubuntu, but has been filed as a bug in Debian. See the bug report here.

Consider double-checking the list of packages that will be installed when installing new software. This behavior has resulted in two bugs in Lubuntu:

  • KWallet and KWalletManager are being installed by default instead of gnome-keyring: Bug link
  • Alacritty is being installed alongside QTerminal: Bug link

Noticed by @arraybolt3, thanks Aaron.

1 Like