This update has fixed my problem with minmizing Thunderbird, locking screen and switching screen off then coming back and not being able to restore Thunderbird. Now works as expected. 🙂

Al good on my Gnome machine 👍

Harvey can confirm, not supported in gnome-terminal

    Kiwimoose You should be able to reach a TTY by pressing e.g. CTRL+ALT+F3. From there I'd first try another full update in case it was incomplete, with sudo eopkg up. If anything new gets installed, then I'd reboot and see if it works. If there are no updates, or the update didn't fix things, I'd do a sudo usysconf run -f to forcibly run all usysconf triggers. If there are no errors, reboot and see if it works now. If it still not works after these steps, I'd list the installed nvidia-packages with eopkg li | grep nvidia and then remove all the listed packages except for ones with -modaliases in the name (those are used for hardware detection and not part of the driver). Then I'd reboot and see if things work without the driver.

    One possible issue is that your EFI partition is too small, and thus the kernel can't be properly updated, while the nvidia modules were, leading to a mismatch. That should show up as an error message when you run usysconf (see above)

        smoothly updated on xfce

        Although the updates were applied smoothly, I didn't realize that the problem with losing the network after a hibernation still persists. So, the hibernate funtion is meaningless. I can shut a computer down at night, and accompllish the same thing - either way, I have to restart everything in the morning.

        I know my memory isn't perfect, but I could swear I solved this problem a little while ago. Seems like it's back.

        I have come with many issues, but most of them were solved.

        I have this remaining problem :

        sep 29 14:10:25 systemd-logind[1010]: Failed to connect to system bus: No such file or directory
sep 29 14:10:25 systemd-logind[1010]: Failed to fully start up daemon: No such file or directory
sep 29 14:10:25 systemd[1]: Failed to start systemd-logind.service - User Login Management.

        Also

        root@solus / # clr-boot-manager update
No kernels detected on system to update

          jacojacker What is the last thing you configured on this system? Did you change desktop environment? Install something weird from outside the repository?

              Staudey Yes, installed Ollama and being on ADM GPU started installing RoCM.

              Not sure if that was the case.

              Although I have managed to get it working the old "windows" way. Reinstalled, updated, and everything went back to normal. (I had my /home on another disk) Thanks!

                  MARIADB UPDATE QUESTION

                  while updating budgie laptop it got to installingmariadb-common and eopkg presented me with a prompt: "Re-install same version of package? (yes/no)"

                  I hit YES and updated finished successfully.
                  QUESTION: Nothing to see here?
                  thank you!

                    jacojacker Yes, installed Ollama

                    Ah well, that'll do it. There was someone on Matrix who also had issues with the ollama installer (or maybe that was you?)

                        Staudey no one has seen the weird solus stuff I've seen...born under a bad sign perhaps..

                          Hello,

                          Is it possible to update Virtualbox to 7.1.2? There are lots of bug fixes.

                          Murat

                            brent

                            I got the same message during my update for Plasma. I anwered, "yes" as well and no harm seemed to result. I no longer remember which package it was in reference to on my system, but I distinctly remember that message.

                                WetGeek thank you for confirming this. like you, I have to assume this meant nothing.