ASDTT I do not understand why when trying to remove nvidia whatever driver eopkg MUST uninstall also doflicky

This is only true for the -modaliases packages, which are used for hardware detection. Don't remove those (they are tiny anyway).

ASDTT DoFlicky I think is part of the problem, since the 390 version of driver removal it always said it found no drivers were found for my system.

Because it's true, there is no supported proprietary NVIDIA driver for this GPU anymore. Nouveau is the only option. None of the proprietary NVIDIA drivers in the repository will work for you.

Check if there are still any of those packages installed with eopkg li | grep nvidia | grep -v modaliases and remove them.

        Staudey Thank you, I'll try when I get home from work. But in all this time I've tried to remove all Nvidia drivers (or at least I think so) and I wasn't able to get to the desktop.

          This is mostly to get you back into a known state, with no non-functional driver packages installed. I suspect the underlying issue that leads to the black screen in the first place is something else. Not sure if the nouveau driver is currently broken somehow (I'll have to test it on my own GPU).

          Staudey So, eopkg li | grep nvidia | grep -v modaliases returns nothing, the only packages are the modaliases.

            Run update 51. Everything stays the same. Get to login screen, write password -> Black screen with mouse pointer. eopkg check doesn't show problems. Going to try and copy the journalctl from a nomodeset session.

            If you switch to a different TTY can you restart lightdm? sudo systemctl restart lightdm.

              Hm, if it were a Budgie component or Mutter crashing, the Fail Whale screen should appear telling you to log back out. Or, you would just get kicked back to the login screen.

              Is the above log still current, and is it the full log? I don't see anything there indicating a crash.

              It's not the most current it's from 72h ago. Yesterday (22 of december) journalctl -p err -b -1 and journalctl -b -1 | grep err gave back
              budgie-session-binary[1726]: Unrecoverable failure in required component org.buddiesofbudgie.BudgiePanel.desktop
              and
              gsd-power[975]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: No se puede invocar al método; el proxy no tiene dueño para un nombre org.gnome.Mutter.DisplayConfigconocido y el proxy se construyó con la opción G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START (g-io-error qurark, 0)

              and also
              gsd-power[1841]: Error setting property 'PowerSaveMode' on interface org.gnome.tter.Displayconfig: No se puede invocar al método; el proy no tiene dueño para un nombre org.gnome.Mutter:DisplayConfigconocido y el proxy se construyó con la opción G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START (g-io-error-quark, 0)

              I suspect there might be some relevant output around the line that says there is an unrecoverable fault in Budgie Panel, likely just above it.

              In addition to that, could you tell me what applets you had on your panel?

                EbonJaeger here are the 2 most recent full journalctl outputs (from one session with current kernel, no other parameter applied and the second one also in current kernel but with nomodeset)

                And these are the applets:

                  11 days later

                  New update, still the same issue. Paste for the journal sessions, last one the only one able to boot to desktop (with nomodeset). Tried reinstalling mutter, budgie-session and desktop and nemo, since there were some warning about them.

                  I am having the exact same problem.

                    james8755 There's a bug report by someone else, but solus team is still trying to solve the problem. Apparently nouveau is having some troubles and they can only recommend proprietary drivers, if available.

                        ASDTT There's a bug report by someone else, but solus team is still trying to solve the problem.

                        The reporter on that issue rolled back to a prior update and re-updated. They no longer have an issue.
                        Can other people affected by this issue try installing the proprietary NVIDIA drivers (for supported GPUs), and report your results in that issue? Thanks.

                            • AASDTT

                              • Post #18

                              TraceyC I've posted it in the git report. Thank you.