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.

        Playing a game using Wine this morning, I noticed my keypresses are sometimes getting 'stuck', like the keydown event is registering but not the keyup, and I have to press the key a second time to cancel it out. I never got this before the update, so I'm inclined to think it's related. Typing out this post has been fine so I don't think it's an overall system problem.

          @EbonJaeger @ReillyBrogan

          • current kernel
          • Budgie edition
          • Intel HD 530, i915 driver
          • secure boot disabled

          Can get to a different tty from the login screen, so here's my journalctl -rb dump pastebin from one of the failed Budgie session boots:

          My budgie panel applets:

          • keyboard language indicator/switcher
          • keyboard lock keys indicator
          • budgie menu
          • icon task list
          • systray, network, volume (sorry, don’t remember if these are separate or not)
          • notifications
          • clock
          • raven trigger

          Not sure if worth mentioning but I also just noticed that when my panel pops in before the desktop gets completely frozen by the memory leak/cpu load caused by budgie-panel, the icon task list applet has been the only applet that's consistently missing from the panel at that stage every single time so far.

          Also what else I've tried to do to, unfortunately, no effect:

          • rolling the update back (eopkg throws a system error: Repo item libatk-32bit not found)
          • reinstalling budgie-desktop
          • reinstalling mesalib
          • booting in with a previous kernel

          Thank you so much for looking into this!

          I was asking about what steps in @EbonJaeger 's post fixed the gnome-mahjongg issue when I realized that it was in answer to a much earlier problem. So I tried to delete my post, but cannot find a way to do that. Is this a new flarum feature? Immutable posts?

            WetGeek

            Referring to this page of the help center, I mounted my system from a live usb of ZorinOs which I happened to have at hand, and chrooted my Solus system.

            Then I followed the first three steps under "Repairing Packages"

            1. sudo eopkg rebuild-db
            2. sudo eopkg up
            3. sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall If you see output that starts with "Usage", this means the system has no broken packages.

            Then I ran sudo eopkg it --reinstall systemd and rebooted.

            That seems to have done the trick.

                • [deleted]

                • Post #62
                • Edited

                inkbug

                Sorry to inform, my budgie vanila-no-longer-vanilla got corrupted again.
                The instructions in the quoted post didn't help me.

                It happens after some installations (not a single thing) but reverting step by step (or trying to) didn't work for me. also not the instructions above regarding reinstalling systemd.

                I tried what's in there, regarding rerolls, reinstall desktop, reinstall systemd to no avail.

                I did not try other stuff as being a newbie it was already difficult enough (and can't remember well so adhering to pages) and I did more and more errors. Personally I have some difficulties in this term especially so couldn't do much reliably.

                Took some screenshots of desktop view at various stages, and will try to edit out some details and post.
                Tried to copy some logs along with those screens (though I am ashamed of some errors) before I install something.

                can right click and go to system settings.
                TTY works. chroot and network works. reroll and reinstall possible, beside for the one listed as upgrade (#1 for me)
                can't revert the big upgrade (1st since vanilla install)
                libatk missing from repo.

                The details of my system and the nature of the error are on upper posts.
                P.S. at this point I can finally vote I have some errors which I could not solve by myself. Giving up for now.
                Another thing I recalled: screenshot shows X11 being used on the corrupt installation.
                Booting from another kernel on the corrupted system (current) did not change its state.

                What I didn't try: reinstalling mesalib, something regarding journal.
                There were no broken packages.

                    inkbug Then I followed the first three steps under "Repairing Packages"

                    Thanks for your reply. Indeed, these are steps to solve a booting problem. That's a much earlier issue than the mouse problem I had confirmed I was having with the gnome-mahjongg solitaire game. @EbonJaeger had written that he has fixed it in the unstable repository, so it's no longer an issue.

                    That's why I wrote to tell you I was trying to respond to a message you wrote about an earlier problem somebody else had. I confused that reference with @Ebonjaeger's more recent message, which didn't contain any "steps" in it.

                    But when I realized that you and I were referring to two different messages from @EbonJaeger, and tried to delete my post (so I wouldn't add to the confusion) I wasn't able to delete it. I'm not having a boot problem at all. Just a mouse problem in that specific game that's already been fixed in the unstable repository.

                      • [deleted]

                      • Post #64
                      • Edited

                      [deleted]
                      On a second thougt, if I feel fit for it later, I'll try "Users who are still experiencing issue with Budgie and are using Intel graphics, does sudo eopkg it mesalib --reinstall help at all?" suggestion (can't quote well) or will see if can bring details regarding journal which at this point I can't.

                      The issue is I can't see the instructions from TTY so it will have to be by chrooting again so it's not "natural" for me.

                        • [deleted]

                        • Post #65
                        • Edited

                        EbonJaeger
                        Regarding method of getting (existing) logs. I had a way. It's not a recommendation, it's for those who may install anyway unless one else who fits to recommend, recommends it.

                        I think I could copy some logs while using a USB live with storage and also decided to take some logs to storage on the session while I was chrooting. Maybe such could be done from an OS on other disk as well, regardless of chrooting maybe too. Somehow. I don't know regarding permissions.
                        But it was easier for me and maybe it is easier than remembering the command but I did that only as a last resort since I'm going to install something else on the system soon anyway.

                        (my backup is OS agnostic as far as I know, so I am not afraid, though it takes some work and apps etc are not backed up in the way I chose, it can still bring back an OS like solus of any flavour/mint/mx, maybe zorin maybe even spiral etc, to function nicely in not so long time after an installation.)

                            Since the latest update Unicode input does not work anymore. I am using a keyboard that sends unicode with special characters and till last update it worked perfect for years. Also direct Unicode input by Ctrl+Shift+u prints u but after entering unicode hex and pressing enter no characer shows, all gets deleted. So I guess there is a problem in IBUS or IBUS configuration. IBUS daemon and related stuff are up and running as far as I could check. Could it be also a GTK problem? I don't know too much about the workings. Help would be appreciated.