SpiralLinux
Stuck after upgrading to debian 13
As the title says, I tried upgrading to latest debian (carefully following spiral's upgrade instructions, of course). After upgrade I get stuck on this screen (see screenshot).
What can I do with this situation and is there a possible eta for 13 based spiral?
P.S. I tried upgrading right after install, so there are no worries about data loss.
Hi there, sorry to hear it didn't work. I can only assume it's some quirk related to upgrading an encrypted installation, which I personally don't use, so it doesn't get tested much.
Yeah, I forgot to add that I used luks encryption option in the installer
If you don't mind running an unencrypted installation then you'll probably have better success upgrading it.
I was planning to install it on my work laptop, so additional security would've been appreciated. If it is installer's problem, couldn't it be fixed somehow?
I honestly don't understand how the Calamares installer implements encryption. There's surely a way to fix the upgraded installation too, but I have very little knowledge of the mechanisms specific to encryption.
I strongly suspect this is the issue: https://www.debian.org/releases/stable/release-notes/issues.html#encrypted-filesystems-need-systemd-cryptsetup-package
Could you please try a fresh encrypted install? After following the instructions again to upgrade to Debian 13 and before rebooting the system please verify if the systemd-cryptsetup package is installed, and if not then install it before upgrading.
Sure thing, I'll try. During upgrade there are also few prompts about updated configs e.g. for plymouth. Do I need to replace those or keep old ones instead? Also is there an estimate for release of spiral 13? I could wait for it if it doesnt take too long to push out
During upgrade there are also few prompts about updated configs e.g. for plymouth. Do I need to replace those or keep old ones instead?
I would usually recommend keeping the SpiralLinux versions.
Also is there an estimate for release of spiral 13? I could wait for it if it doesnt take too long to push out
No estimate yet, and there won't be any major new tweaks, so you might as well install the current version and upgrade it.
Boot in recovery mode to see why gdm is failing (for me some libglib dependency). boot to shell, purge and reinstall gdm fixed my issues. All systems up and running now, after 10 attempts to upgrade.
@jurgens1312 are you also using the encrypted setup?
@benadrylcabbagepatch have you found the solutions?
I just upgraded to trixie following the istructions but after reboot my desktop is extremely lagging.
I'm not opening an issue because it depended on Wayland on Plasma6, which is now the default on Debian 13. I switched back to X11 and the lag disappeared.
I can report that the upgrade to Trixie was possible without any problems and without the need to install the systemd-cryptsetup package:
- https://github.com/orgs/SpiralLinux/discussions/567#discussioncomment-14366484
Thanks @marwenius for confirming, so in that case it must be the GDM issue that @jurgens1312 mentioned.
Sorry it took a while, I was away and busy on other stuff.. So I tried installing spiral linux again with gnome de, this time without using any encryption. Unfortunately after upgrading it still hangs on the same screen I posted above, ending with "gdm.service"
Hmm, I wonder if it has to do with Wayland being disabled. Please try putting a # in front of the line that reads WaylandEnable=false in /etc/gdm3/daemon.conf .
This fixed the issue, the system booted! Is there a particular reason why wayland was disabled? Gnome 48 dropped x11 support and brought it back in 49, planning to drop it again soon
Okay, prob another issue but after changing repos from bookworm to trixie and attempting to update through synapse I got an error while updating a particular package (didn't note which exactly). I rebooted and now system boots into black screen, nothing at all.. This is starting to get frustrating for me
Is there a particular reason why wayland was disabled?
Yep. https://github.com/orgs/SpiralLinux/discussions/316#discussioncomment-7215164
after changing repos from bookworm to trixie and attempting to update through synapse I got an error while updating a particular package
I thought this issue began after you already upgraded the system?
I rebooted and now system boots into black screen
Did you install with Btrfs? In that case: https://github.com/SpiralLinux/SpiralLinux-project/wiki#working-with-btrfs-snapshots-and-rollbacks
Yep. github.com/orgs/SpiralLinux/discussions/316#discussioncomment-7215164
That's reasonable, but its almost 2026 and wayland should be in a better shape than back in 2023?
I thought this issue began after you already upgraded the system?
That's correct, after upgrading I commented out the line in daemon.conf and rebooted, everything was fine this time. Then I proceeded to change repos from bookworm to trixie in synapse, like instructed in spiral linux' wiki, no issues here either. After that I refreshed the list and applied all updates, one error occured near the end. I thought that I might reboot and try again, but after grub its just black screen
Did you install with Btrfs? In that case: SpiralLinux/SpiralLinux-project/wiki#working-with-btrfs-snapshots-and-rollbacks
I have, I'll try it thanks
@jurgens1312 are you also using the encrypted setup?
One machine with, one without. It's a Gnome (config) issue. Decryption happens way earlier that the issue you are experiencing. As I recommended, boot in recovery-mode to find what part/dependency of gdm is causing it, then fix that or just purge and reinstall like I did.
@geckolinux i caught another one upon setting up an older thinkpad. same error as the others iirc.
Thanks @jurgens1312 for helping identify the real issue. This should be the solution: https://github.com/SpiralLinux/SpiralLinux-project/issues/566#issuecomment-3305440329
If anybody sees this before upgrading the Gnome edition, the easiest solution would probably be to accept the new version of /etc/gdm3/daemon.conf when prompted to select how to proceed with the config file version.