Your system is non-standard, as you've NOT performed normal release- upgrades, which run modify scripts as you release-upgrade to a newer release; and not just upgrade packages.
You mention modifying sources as you do in Debian, but that is only 'reliable' in Ubuntu for the very early days of a release cycle, OR before a newer release has changed enough that the upgrade scripts also need to be run. Your details show that, ie. > UpgradeStatus: Upgraded to stonking on 2026-01-18 (245 days ago) stonking didn't exist 245 days ago.. If I explore my own system (that I'm using now) it tells me I release-upgraded to stonking on 3 Jun 2026 ; which is possible as repositories both existed then & the metadata shows my machine did run scripts (date & time of that; your last run was 245 days ago in comparison where the development release was resolute so at best that was the 'newest' release-upgrade script you ran. You upgraded the packages on your system (due to modification of sources) which is part of the normal process, but your method did NOT run the specific release script that updated a 'resolute' install to 'stonking' which is Ubuntu specific, AND release specific (ie. that script will differ from questing to resolute as different things change in each cycle).. Your Debian-method puts your system in an unknown & potentially different state to what is expected, not everything maybe upgraded with parts of your system still matching the older release on disk (as script wasn't run during release-upgrade), but your code/packages was updated, and your upgrade method may explain your non-standard state. Confirmation may thus be required to see your issue wasn't self-created. FYI: When I'm using the Lubuntu session on this box; I'm using the Xorg/X11 session normally; as I am on another install where I use stonking. I'm actually happier using Xorg/X11 myself (with LXQt for now), as there is at least one app that I use on occasion that cannot run in Wayland. I'm only using a Wayland session (with LXQt) on occasion as it allows me to test wa little whilst I do what I normally do. I have noticed difference between my main system (correct release- upgrades), some newer-QA installs & a non-destructive re-install, but for now I don't have anything concrete to file bug on (your bug here reminded me of it; but your Debian-method upgrade could explain your state too & I've not tried what you did). For me to see what you describe is a problem, I'd need to install an older release, then release-upgrade CORRECTLY to see what happens (run- do-release-upgrade etc), and if it is identical to what you experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167803 Title: Session menu offers 6 options, only two working, if that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/2167803/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
