that did not work sadly. I did journalctl --unit=lightdm and got this: "Nvidia: failed to initialize the Nvidia kernel Module. Please see the system's kernel log for additional error messages(...)"
And then later:
Fatal server error:
(EE) no screens found(EE)

    Kiwimoose Are you sure you don't have the nvidia drivers installed? What does eopkg li | grep nvidia say? Are there any packages without "modaliases" in the name?

      Damn sorry about that so apparently I had installed the driver while trying to fix this. However with the driver uninstalled it still only boots to a blinking line... made some photos of parts of journalctl that looked informative:

        Kiwimoose a small heads up about this. Booting with nomodeset had the same result. Also with the failed to load module "nv" error (idk if that's even relevant). Also I've been running this install of Solus for a really really long time now (might even be a decade) and I believe that maybe the default display manager used to be gdm at one point and maybe that's causing issues? But no idea...

            Harvey

            I would like to briefly say how great I think your work is! Just returned home, I start my computer and immediately I am offered a "security update". The CVE number was published today and immediately the fix lands on my system. Incidents like these in particular always give me a secure feeling that I am in good hands with Solus. I have often found many and also current packages in the repository, even niche ones. Fairly up-to-date kernels and fast response to security incidents. These are reasons why I believe in Solus and recommend it to family and friends again and again. Many thanks to all of you, the whole team for your commitment!

              ReillyBrogan thanks for the help! I'm a bit embarrassed to say that apparently the issue was me having run out of disc space during the upgrade. I noticed when trying to save a log as a text file. Then freeing up space, checking for broken packages + update and redoing usysconf triggers was enough. Sorry about that and thanks again for the speedy help!

                EbonJaeger the curious cat in me wants to know what was so urgent about Yaru on a Wednesday?

                    brent

                    Nothing. There were other changes such as to calamares which you would not have noticed that we need for ISO testing, yaru just so happened to be in unstable when the sync occured.

                        As far as I understand, there will be no updates this week, and there will be an ISO image release? Or will the ISO image be released next week?

                        PS: We are also looking forward to Plasma 6.2 in future updates. ✌️

                          MrAiupov PS: We are also looking forward to Plasma 6.2 in future updates. ✌️

                          It's officially out, so it's possible to get it in next friday sync 😉

                            MrAiupov PS: We are also looking forward to Plasma 6.2 in future updates. ✌️

                            It SHOULD (huge caveat that this could change at any time) land around the 10/25 sync, or the 11/8 one if it seems like it needs a little bit more time.