I got an initrd error that brick my system. I manage to log in with previous .conf

I'm unsure how to debug/log reading it as I never had that kind of error before.

    Two machines laptop with Budgie and desktop with Gnome both updated fine.

    No problems to report 🙂

    SethStorm666 I got an initrd error that brick my system. I manage to log in with previous .conf

    I'm unsure how to debug/log reading it as I never had that kind of error before.

    Have you fixed it or is it still bricked Seth. Must admit I am doing a Rescuezilla back up each week.

        SethStorm666 When the error screen appear, hit <ctrl>+<alt><F7>
        Then choose previous .conf file

        Good to know. 🙂

          Veracrypt has Update and includes wayland

          Maybe Solus update it for the wayland users

          Aw, fsck!

          Although everything installed okay, as I said up above, not all is working okay now. Friday night I hibernated my laptop, as usual, and Saturday morning it appeared to restore normally - all workspaces, all apps just th way I left them the night before, etc. Then I got the message that there's "no Internet."

          Indeed, I wasn't connected, and couldn't connect until I shut down and restarted the laptop. I thought it might be a one-time glitch, or I'd done something wrong myself, and since everything was now working well, I went on with my Saturday chores, and forgot all about it.

          Saturday night, as usual, I again hibernated the laptop, and Sunday morning it again appeared to restore everything correctly -- until I tried to access the network. Once more, there was "no Internet" and I now realized it wasn't a one-time glitch. I rebooted, but that didn't resolve anything. So I shut down the laptop and restarted it, after which everything worked properly again. This had never happened before this most recent update.

          I don't know whether this is a Solus issue, or a KDE issue. I'd be interested to hear from anyone else who has had the same problem, especially if you're running a different DE than Plasma.

            WetGeek Then I got the message that there's "no Internet."

            Thinking that this might have something to do with the procedure that copies all of RAM to the swap area, I carefully avoided hibernating my computer last night. Instead, I just had it "sleep" instead. Since that avoids the storage and retrieval of all the RAM, I thought it might avoid the error as well.

            But it didn't. This morning, I got the same "No internet" error screen when I tried to use the laptop. So I simply shut it down and restarted, and indeed, the network was fine.

            So, apparently the hibrnation is a red herring that has nothing to do with the problem. It's 100% reproducible without hibernating.

              EbonJaeger unstickied the discussion .