It seems that this bug partly got fixed by some other change than the Ubuntu Release Upgrader while the attached MP was in review. However, I'm still noticing another problem: if a user selects `lightdm` (rather than the new `sddm`) during the debconf prompt during the upgrade, the bug still appears.
** Description changed: [ Impact ] * This bug leads to users inadvertently getting put in a TTY upon reboot - after upgrading a Ubuntu Budgie system from 24.04 LTS to 26.04 LTS. - Additionally it prevents the `ubuntu-budgie-desktop-minimal` package from - upgrading correctly, keeping it held back. + after upgrading a Ubuntu Budgie system from 24.04 LTS to 26.04 LTS. + Additionally it prevents the `ubuntu-budgie-desktop-minimal` package from + upgrading correctly, keeping it held back. * The bug itself is a consequence of `ubuntu-budgie-desktop-minimal` moving - from `initramfs-tools` to `dracut` between 24.04 LTS and 26.04 LTS, and these - packages conflict with each other. Thus a user on 24.04 LTS upgrading will - have `initramfs-tools` installed, but the resolver will by default refuse - to remove this in favor of `dracut`, meaning that the metapackage is held - back. + from `initramfs-tools` to `dracut` between 24.04 LTS and 26.04 LTS, and these + packages conflict with each other. Thus a user on 24.04 LTS upgrading will + have `initramfs-tools` installed, but the resolver will by default refuse + to remove this in favor of `dracut`, meaning that the metapackage is held + back. * The fix is to mark `dracut` for install explicitly on systems using - having `ubuntu-budgie-desktop-minimal` installed, which allows the upgrader - to also upgrade the metapackage. It is justified as the bug itself imposes a - heavy UI/UX regression for desktop users, as they risk being both surprised - and worried in terms of whether their system is broken. - + having `ubuntu-budgie-desktop-minimal` installed, which allows the upgrader + to also upgrade the metapackage. It is justified as the bug itself imposes a + heavy UI/UX regression for desktop users, as they risk being both surprised + and worried in terms of whether their system is broken. [ Test Plan ] ## Reproduction steps 1. Launch a VM using the Ubuntu Budgie 24.04 LTS desktop ISO - (https://cdimage.ubuntu.com/ubuntu-budgie/releases/24.04.5/release/ubuntu-budgie-24.04.5-desktop-amd64.iso) + (https://cdimage.ubuntu.com/ubuntu-budgie/releases/24.04.5/release/ubuntu-budgie-24.04.5-desktop-amd64.iso) 2. Go through the installation (make sure to backup the installed image as it - will be needed for verifying the fix) + will be needed for verifying the fix) 3. Upgrade to 26.04 LTS using: $ do-release-upgrade --devel-release - 4. Say 'y' to removing obsolete packages at the end of the upgrade + 4. Choose `lightdm` as your desktop manager during the debconf prompt - 5. Reboot. Observe that the system will have landed into a TTY + 5. Say 'y' to removing obsolete packages at the end of the upgrade + + 6. Reboot. Observe that the system will have landed into a TTY ## Verification steps 1. Restore the 24.04 LTS from the backup mentioned in the reproduction - steps and launch the VM + steps and launch the VM 2. Upgrade to 26.04 LTS using: $ do-release-upgrade --proposed - 3. Say 'y' to removing obsolete packages at the end of the upgrade + 3. Choose `lightdm` as your desktop manager during the debconf prompt - 4. Reboot. Observe that the system lands in a dedicated desktop manager, - rather than a TTY + 4. Say 'y' to removing obsolete packages at the end of the upgrade + + 5. Reboot. Observe that the system lands in a dedicated desktop manager, + rather than a TTY [ Where problems could occur ] * The biggest risk in this upload is that the `ubuntu-budgie-desktop-minimal` - metapackage has previously not been upgraded correctly, and thus any untested - changes related to this package may surface uncaught errors. More - specifically, these are the packages that differ between versions: + metapackage has previously not been upgraded correctly, and thus any untested + changes related to this package may surface uncaught errors. More + specifically, these are the packages that differ between versions: - 24.04 LTS | 26.04 LTS - # Moved - initramfs-tools -> dracut + 24.04 LTS | 26.04 LTS + # Moved + initramfs-tools -> dracut - # Removed - dmz-cursor-theme -> (removed) - lightdm-theme -> (removed) - tilix -> (removed) - wireless-tools -> (removed) - xorg -> (removed) - xserver-xorg-input-libinput -> (removed) + # Removed + dmz-cursor-theme -> (removed) + lightdm-theme -> (removed) + tilix -> (removed) + wireless-tools -> (removed) + xorg -> (removed) + xserver-xorg-input-libinput -> (removed) - # Newly installed - (n/a) -> budgie-extras-daemon - (n/a) -> desktop-services - (n/a) -> iw - (n/a) -> libqt6wlshellintegration6 - (n/a) -> wdisplays + # Newly installed + (n/a) -> budgie-extras-daemon + (n/a) -> desktop-services + (n/a) -> iw + (n/a) -> libqt6wlshellintegration6 + (n/a) -> wdisplays [ Other Info ] * N/A [ Original Description ] Reported by end-users and verified by myself ubuntu budgie 24.04.4 & ubuntu budgie 25.10 Ubuntu Budgie users who have previously performed a minimal install via the installer minimal option are left at a TTY after reboot post upgrade. If the user examines the list of packages to be cleaned up this includes the critical packages sddm and budgie-sddm-theme. For ubuntu budgie we have moved from lightdm to sddm - lightdm is no longer part of our seeds. sddm and budgie-sddm-theme (the sddm greeter) are recommendations in the seeds. ---- debugging - I have experimented in stonking making sddm and budgie-sddm- theme dependencies rather than recommendations. I switched from sddm to lightdm in 26.04 before the upgrade, purged sddm & budgie-sddm-theme and apt-mark lightdm as auto - i.e. trying to reproduce the conditions on 24.04 and 25.10. On a do-release-upgrade -d I can see that sddm and budgie-sddm-theme are processed as part of the seed installs, lightdm is processed afterwards as part of the do-release-upgrade package cleanup. This means I can't use a postinst in budgie-sddm-theme to make systemctl enable sddm. It appears lightdm removal leaves sddm disabled - /etc/X11/default- display-manager is indeed equal to the value "/usr/bin/sddm" after lightdm removal. There is no /etc/systemd/system/display- manager.service file, so lightdm removal is doing something funky? Happy to revert that stonking change to make sddm and budgie-sddm-theme recommendations again. ---- on matrix skia mentioned possibly using a quirk - but I have no experience of this and wouldn't know which section would be appropriate nor how to test - also I'm guessing both 24.04 and 25.10 ubuntu-release- upgrader needs to be updated? Marking this as critical since the end-user are left with an unusable post release upgrade. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: ubuntu-release-upgrader-core 1:26.04.18 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: Budgie Date: Sun Jun 14 20:39:02 2026 InstallationDate: Installed on 2026-04-05 (70 days ago) InstallationMedia: Ubuntu-Budgie 26.04 "Resolute Raccoon" - Daily amd64 (20260402) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) ** Tags removed: verification-needed-resolute ** Tags added: verification-failed-resolute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2156727 Title: [SRU] upgrade from 24.04/25.10 leaves the user at a TTY To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2156727/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
