r3laps3 Maybe try going to TTY and running sudo eopkg it nvidia-glx-driver-current then sudo eopkg it nvidia-glx-driver-common and sudo eopkg it nvidia-glx-driver-32bit

Ran the commands and output from eopkg li | grep nvidia was the same 5 lines as above.

Loading still failed to progress but rather than a blank screen with a mouse, was left with just a blank screen and text-based cursor. So not sure if that is progress or not!

Created 2 x live USB drives, 1 x Tails, a Debian-based distro that apparently doesn't like Nvidia, and 1 x Solus/Budgie using the latest download. Tails fired up and ran without any issues, as did Solus from the live USB but I noticed during the Solus startup, a message flash on the screen prior to the initial display (alpine lake) along the lines of:
failed-to-start[flatpak-enabled-flathub-service] Add Flathub flatpak repositories

I run Librewolf as a flatpak on the PC having the issue so not sure whether this could be related. Startup on the PC does not seem to progress to this point.

      The next sync will include a kernel update, hopefully that helps with some of these issues.

      b23 Ran the commands and output from eopkg li | grep nvidia was the same 5 lines as above.

      Loading still failed to progress but rather than a blank screen with a mouse, was left with just a blank screen and text-based cursor. So not sure if that is progress or not!

      You should uninstall the nvidia driver packages, your GPU is too old for any of them. Sorry, I should've read your original post closer before I first asked, and realized that it's a 500 series card.

      sudo eopkg rm nvidia-glx-driver-common

      b23 failed-to-start[flatpak-enabled-flathub-service] Add Flathub flatpak repositories

      That error can be ignored, just a minor issue with the service responsible for automatically enabling the flathub repository, which hasn't been fully figured out yet (but has no negative consequences apart from that message showing up)

            Staudey You should uninstall the nvidia driver packages,

            Ran and now left with the 2 x 'driver-modaliases' entries as originally shown.

            Also ran sudo eopkg up which applied over 1GB of changes so up to 4.6 Convergence (6.12.5-311.current). After rebooting, and immediately after logging in, PC displays a blank screen so is back to the initial problem with a blank screen and the (movable) mouse cursor.

            To power down, I have to hold the PCs power button, although I can power off from the top right of the logon screen before logging on. All functionality seems to be available, and everything looks as it was previously, up to when I log in. The blank screen with mouse then appears and nothing further is possible.

              If after logging in is a problem, maybe the fault is with your profile. I suggest creating a new user in TTY and log in to him.

                pomon I've tried this and the problem continues.

                  Staudey but has no negative consequences apart from that message showing up

                  That, and a very long timeout before the boot continues. I'll be glad when it's sorted out.

                    Well, still:

                    1. Show eopkg li | grep mesa and Make sudo eopkg it --reinstall mesalib mesalib-32bit
                    2. Install linux-lts and switch to it.
                    3. Show how it looks after logging in. Make a screen with a phone.
                    4. Uninstall NVIDIA drivers if you haven't done it yet.
                    5. You need to search the logs, e.g. journalctl -p err -b -1 orjournalctl -b -1 | grep err. You must read about journalctl.

                    Ps. And actually I don't know who the problem @b23 or @ASDTT

                      pomon grep li mesa gives mesa-demos, mesalib and mesalib-32bit. Drivers were uninstalled since 390 was deprecated, and grep nvidia only shows the modaliases.


                      The screen after booting to 6.6.66-262-.lts and typing the password on login.

                      As I said in the other post I first made, journalctl gives lots of budgie-session-binary[866]: WARNING: APPLICATION... then either or.gnome.SettingsDaemon.(XSettings...) or org.buddiesofbudgie.Budgie(Wm, Panel, Daemon,Polkit) and one Unrecoverable failure in required component org.buddiesofbudgie.BudgiePanel.despktop

                      Exactly by applying your suggested command 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)

                        11 days later

                        • Bb23

                          • Post #16

                          pomon You need to search the logs, e.g. journalctl -p err -b -1 or journalctl -b -1 | grep err. You must read about journalctl.

                          Returned just the one response:
                          Unrecoverable failure in required component org.buddiesofbudgie.BudgiePanel.desktop

                          BudgiePanel was the entry showing up in the system resource monitor whose RAM consumption increased over a few days from hundreds of MB to several GB while other processes (browser, VPN...) remained essentially constant.

                          Possibly a memory leak? Seems strange I can't restart, log back on and reuse as before as the reboot has cleared the memory use issue in the past.

                            7 days later

                            • Bb23

                              • Post #17

                              pomon Running from a live USB for testing - user "live".

                              Test 1

                              1. Ran Solus from a live USB with no issues running or performing tasks.
                                ![
                                ]

                              2. Ran System-Monitor to monitor memory use by budgie-panel as this was referenced in the only error from the installed version.
                                Unrecoverable failure in required component org.buddiesofbudgie.BudgiePanel.desktop

                              3. Memory use by budgie-panel increased significantly from about 65MB over a couple of days with little PC use.

                              4. Turned off all notifications. Memory in use by budgie-panel then stabilised at 624.1MB.
                                5, Shutdown the PC.

                              Test 2

                              1. Ran Solus again from the same live USB with no issues getting up and running or performing tasks.
                              2. Turned off all notifications except for disks and network.
                              3. Ran System-Monitor to monitor memory consumption. Memory in use by budgie-panel increased to over 100MB.
                              4. Turned off network notifications leaving only 'disk'. Memory in use by budgie-panel continued to increase although there were no notifications.
                              5. The main Budgie menu and running apps - System-Monitor, Terminal, Firefox - then became unresponsive. The budgie-panel process disappeared from the list of processes in System-Monitor (below in alphabetical order)

                                Will run further tests tomorrow using the live USB. There don't appear to be initial issues with this approach - no black screen with just the mouse cursor after logging on - although it is rather slow.
                                24 days later

                                • Bb23

                                  • Post #18

                                  Running nohup budgie-panel --reset --replace & (process above with increasing memory consumption) gave the following errors

                                  (budgie-panel:1979): Gtk-WARNING **: 11:45:08.103: cannot open display:

                                  (budgie-panel:2095): Gtk-WARNING **: 11:46:57.659: cannot open display:

                                  Running xhost +localhost xhosts + gave the error

                                  xhost unable to open display

                                  The PC will run Solus/Budgie from a live USB without any issues (as has always done in the past) if I use the Solus-Budgie-Release-2024-10-14 iso but gives the black screen when running a live USB using the latest Solus-Budgie-Release-2025-01-26 iso. Both live USBs are on identical 8GB microSD cards through a card reader plugged into a USB port.

                                  It seems a change occurring between the release of these 2 iso's is impacting the display of any outputs from the point where I log in and that's where I get to with the installed version.

                                  Any ideas to help solve would be appreciated. as I would like to get the PC operational again.

                                  8 days later