For people experiencing issues (it sounds like mostly Budgie users?) it would be great to report the following:

  • Whether you're on the LTS or current kernel
  • DE (Budgie, GNOME, Plasma, Other?)
  • GPU and GPU driver
  • Whether or not you have secure boot enabled

For debugging purposes you can edit the kernel arguments by holding the down key while booting. The most recent -current kernel is 6.3.12-244. You can try to boot with an older kernel to see if that helps (please report back which ones work for you). You can also try hitting e over the boot entry to change the kernel options. If you're using a nvidia GPU we recently added the nvidia-drm.modeset=1 parameter, try deleting that and see if that helps. You can also remove quiet loglevel=3 splash systemd.show_status=false to get more verbose logging which can help debug the issue.

For people who are not able to log into a session are you still able to switch to a different TTY and log in there (hitting CTRL+ALT+F3 for example)? That will help us understand where exactly this issue is happening.

    ReillyBrogan Whether you're on the LTS or current kernel
    DE (Budgie, GNOME, Plasma, Other?)
    GPU and GPU driver
    Whether or not you have secure boot enabled

    Kernel: 6.3.12-244.current
    DE: Budgie
    CPU: Intel Core i3-3110M
    GPU: Intel 3rd Gen Core processor Graphics - driver: i915 - API: OpenGL v: 4.2 Mesa 23.1.4 renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    Secure Boot: Was disabled, I enabled it following the guide for existing installs. Now it boots correctly as I already enrolled the cert wen clr-boot-manager, version: 3.2.12, release: 29 was available in the stable repo.

        nolan checking for brocken packages

        I should say I was in TTY ctrl+alt+[function key]

          nolan Which issues did you have specifically? And which ones have you resolved?

            • [deleted]

            • Post #42
            • Edited

            ReillyBrogan
            Warning ahead, can't troubleshoot as I don't have the problematic install
            The following refers to my previous install which had issues with this update.

            Whether you're on the LTS or current kernel

            Current (Shannon)
            6.3.12-244.current
            Trying the previous stable one didn't help after the update

            DE (Budgie, GNOME, Plasma, Other?)

            Budgie 10.7.2

            GPU and GPU driver

            Intel® UHD Graphics 620 (KBL GT2)
            I believe the drivers were, non formally, that mesa and that i915. (default, updated with the system)

            I believe the following was true also for the previous install:
            driver: i915
            loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
            resolution: 1366x76860Hz
            API: OpenGL v: 4.6 Mesa 23.1.4 renderer: Mesa Intel UHD Graphics 620 (KBL
            GT2)

            Whether or not you have secure boot enabled.

            I didn't have secure boot enabled (and still don't)
            I do have a UEFI/GPT/Solus automatic full disk (previous time with Luks, LVM) installation.

            Also, had Luks and LVM (now I don't use).

            Could login, but couldn't use the desktop once logged in. Mouse cursor moved and that's it. icon panels were missing, mouse clicks didn't do anything or were not captured etc (non formal description). I didn't know enough/though to check keyboard by then.

                For Budgie people having login problems where you get the Oh No screen, what we really need are journal logs which should point us in the right direction.

                1. Attempt to log in
                2. Get to Oh No screen
                3. Switch to a TTY (Ctrl+Alt+F2)
                4. journalctl -xe and look for errors; most probably a SEGFAULT

                The trick will be figuring out how to post the logs, given you can't start a Budgie session... The best you can do might be to take a picture of the screen with a phone and use that to post to the forums. Not ideal, but...

                If anyone else has a better idea to get logs, please share.

                  regarding to the boot issue, I took a picture [too big here]
                  it said:

                  [!!!!!!] Failed to start up manager.
[  15.188781] systemd[1]: Feezing execution.

                  was the only in the screen.

                  I thought it could be some issue it the bios (uefi configuration) I guess I disabled secure boot or something else, I managed to boot selecting the disc drive instead of the solus boot manager(uefi), Checked for broken packages and as I said

                  nolan font-weather-icons-otf

                  was broken, reinstalled it with --reinstall , rebooted and selecting the disck drive again, booted to desktop as normal, shut down and boot a few times to ensure it was OK, no problems after that.

                  Then followed the guide for enabling secure boot in an existing installation, I updated clr-boot-manager clr-boot-manager update maybe it fixed the problem? I'm not sure at this point.

                    • [deleted]

                    • Post #46
                    • Edited

                    [deleted]
                    I forgot:

                    on chroot, made the 1st steps as written and then I had eopkg check with no broken package. I did notice the upgrade removed package, no idea if that is OK, it could be.

                    Anyway in time I was asked to in instruction, I did trigger the things which are triggered after update as was asked, I think I exit as had to, and rebooted, (I don't remember the orders, but those I followed,) instruction said don't reroll unless issue was not solved by those previous steps and a reboot, it didn't solve the issue, but from that point I messed up by my fault before even getting to try the actual reroll.

                    CPU I forgot to add (the rest of the info, above)
                    CPU:
                    Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP cache:
                    L2: 1024 KiB

                      nolan I'm on desktop now, no problems on my end at the time.
                      EDIT: the dates are wrong, it's not today [29] it's yesterday [28] that is useless now.

                        I'm a Budgie desktop user, 216 updates, 1.55 GiB processed today.

                        After rebooting, I encountered a problem on Redshift, reported by @brent :
                        I had the message "Failed ro run Redshift. Trying location provider 'geoclue2'... Unable to get location from provider".

                        On @Staudey 's wise advice, I set the command

                        /usr/lib/geoclue/geoclue-2.0/demos/agent

                        to autostart in Budgie Desktop Settings, but I had to reboot my computer, because otherwise I couldn't play my music or videos (application screen frozen). The problem is now solved for redshift after reboot, it's an interesting application which has the advantage of gently and gradually reddening the screen in the evening.

                        If I notice anything else, I'll be sure to let you know.

                        In any case, thank you and congratulations to the Solus developer teams, well aware of the hard work provided, which fully justifies the absence of updates last week.
                        I would also like to salute the effort to inform users, made each week by these teams concerning these updates. @WetGeek had asked for it with insistence, he was right, thanks to him too.

                        I use arc-gtk-theme as my Gnome Shell theme. It works great as a gtk theme, but for Gnome Shell it broke with the upgrade to 44. This is minor and also an upstream issue, so no problem here. Just switched to the default shell theme for now. Everything else went smooth, thanks for the huge amount of upgrades!

                        Users who are still experiencing issue with Budgie and are using Intel graphics, does sudo eopkg it mesalib --reinstall help at all?

                        Staudey Seems like this was already an issue in the past with a geoclue update (that's why it was reverted here). Unfortunately it seems the redshift app no longer sees any development.

                        edit: Arch Wiki describes a workaround here: https://wiki.archlinux.org/title/redshift#Automatic_location_based_on_GeoClue2
                        (but note that the location is apparently different in Solus: /usr/lib/geoclue/geoclue-2.0/demos/agent)

                        Staudey I added the command for geoclue and it worked, thank you. If Redshift is being neglected then its a perfect time for me to migrate to Budgie's NightLight. thanks for the info

                          Another bug found on Budgie Desktop concerning the Mahjongg game: it's not possible to click anywhere other than on the middle pawn, as shown below:

                          And of course, you can't play to it !
                          I specify that I played it this week before update without encountering this problem.
                          Thank you in advance for your help, but of course, there is no emergency. 😉

                            penny-farthing And of course, you can't play to it !

                            Confirming this for myself and my wife. She tried to play gnome-mahjongg this morning, and I thought it was just her laptop acting up. But after seeing this post in the forum, I checked my laptop as well, and sure enough, it affects me, too. I just hadn't tried to play any of these games today.