Hi everyone!

I've been a Solus Budgie (and Linux!) user for a couple of months now, and have been loving my experience so far. Unfortunately, I've had my first hiccough today after installing the latest updates.

After eopkg did its thing, I rebooted and am now experiencing very lengthy boot-to-desktop times, which feel like 2-5 minutes. My screens will stay black during this whole time, right until the desktop loads. Sometimes, Solus will loop over the login screen (I believe it might be the lightdm login screen?).

I'm not sure if this might hint at something wrong, but curiously after the update, Meson is "Unable to determine dynamic linker" when I try to meson builddir even though I was happily using Meson right before I updated minutes beforehand.

I am on an i5-6600k and nvidia gtx 970. I'm not sure what logs to provide, so please let me know and I'll post back as soon as I can 😃

Thanks in advance!

I have the same issue. It took a couple of minutes to get to the login screen. Then around 20 seconds after entry of the password to get to a black screen with just the cursor visible. Then after another minute or so the cursor went away. Then it loops back to the login screen, which logs in at the normal speed, but the desktop is still blank with cursor, which then goes away.

On the third time of doing that the normal ui displayed and the response time was normal.

After a restart, the couple of minutes load up time remain, but the UI comes up after first login.

Computer is a dual boot windows, i5 7th gen, with 750ti.

This should already be fixed with an update to systemd that should've been cherrypicked by @DataDrake to stable last night.

    I don't have any issues on my Laptop, so it seems to be related to some specific components or software. My (quite old) laptop has an i5-460M and ATI MobilityRadeon HD5650.
    There is another new post eopkg looks very unreliable about lots of broken packages after the new update, maybe it's related issue? Just checked and found no broken packages on my system.

      Right, managed to get a network connection on my laptop while I'm away. I did an out-of-band sync so you folks wouldn't have to wait until tonight. Should be sorted now. Thanks @Staudey for the fix ❤️

      elfprince For all its hiccups it is bar none the best service, device, boot, etc. orchestration system on Linux (service management is just a small part). I wouldn't want to replace it with inferior options like runit OpenRC or regress to the days of Upstart and SysVInit.

          Woke up this morning and ran the updates. They worked as expected and boot times are back to normal 👍️
          Thanks everyone!

          When reporting the issue to systemd I almost thought that I was the only user affected and it was something incredibly specific about my setup. Glad that the fix also helped some other people.

            JoshStrobl Wow, I wasn't aware that you had such a high opinion of systemd. All this time I've read that distros are just 'putting up with it', and simply going with the flow (ie following the example of the major distros). I trust your (and other devs) technical expertise, and will relax (a little) about it. 😁