You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Debian 12 Bookworm was released last week I have upgraded 6 Debian systems, including 2 based on the first release of the KDE version of Spiral. The straight Debian upgrades were mostly extremely smooth, as were the Spiral upgrades, with one rather annoying exception.
A network service would grind away for 2 minutes until it timed out and the system booted normally. I investigated with:
The network and my fstab-mounted LAN share worked just fine without this service and the system boots like it always did.
Which is to say, rather slowly because I chose LUKS encryption & the way Calamares handled the encryption means I have to wait about 30-40 seconds after entering my encryption key to get to the Grub screen; it I fat-finger my decryption password I get to wait a minute or so and the system drops me to a grub rescue prompt, rather than letting me enter my password again. With my straight Debian systems it creates an annoying unencrypted ext2 boot partition, but the systems boots instantly as soon as I enter my password and if I muck up the PW entry it gives me another couple of chances before it times out for a minute or something.
That said, the latest actual Debian release having caged several ideas from SL like official live media, default proprietary firmware & the Calamares installer at least on the live ISO, the encrypted install behaves exactly the same annoying way it does on Spirallinux, but hopefully now that there are more eyes on the issue something can be done (I wish I were more hopeful).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Since Debian 12 Bookworm was released last week I have upgraded 6 Debian systems, including 2 based on the first release of the KDE version of Spiral. The straight Debian upgrades were mostly extremely smooth, as were the Spiral upgrades, with one rather annoying exception.
A network service would grind away for 2 minutes until it timed out and the system booted normally. I investigated with:
systemd-analyze critical-chain
└─network-online.target @2min 1.207s
What worked for me was disabling the service:
sudo systemctl disable systemd-networkd-wait-online.service
The network and my fstab-mounted LAN share worked just fine without this service and the system boots like it always did.
Which is to say, rather slowly because I chose LUKS encryption & the way Calamares handled the encryption means I have to wait about 30-40 seconds after entering my encryption key to get to the Grub screen; it I fat-finger my decryption password I get to wait a minute or so and the system drops me to a grub rescue prompt, rather than letting me enter my password again. With my straight Debian systems it creates an annoying unencrypted ext2 boot partition, but the systems boots instantly as soon as I enter my password and if I muck up the PW entry it gives me another couple of chances before it times out for a minute or something.
That said, the latest actual Debian release having caged several ideas from SL like official live media, default proprietary firmware & the Calamares installer at least on the live ISO, the encrypted install behaves exactly the same annoying way it does on Spirallinux, but hopefully now that there are more eyes on the issue something can be done (I wish I were more hopeful).
Beta Was this translation helpful? Give feedback.
All reactions