Bhibb I don't know. I wasn't following that issue closely, but my understanding was that it is a Budgie only issue, while I am running GNOME.

    bubba66 Filed an issue on the Budgie Desktop tracker here. If you're on GitHub, you may want to follow that issue and chime in. 🙂

        After today's sync I'm having issues with my bottom panel (Budgie). For years I've had the task list icons as 50x50 while the icons in the system tray were smaller, something like 32x32 if I had to guess. Now those two separate sets of icons, with different purposes are locked at the same size, and I can't keep the larger task list icons with the system tray icons remaining smaller. To me, personally, this makes no sense--the system tray icons being much smaller than the running application/task list icons makes more sense to me and I think it looks much better.

        Is there any way I can force these two sets of icons to be different sizes again? I really, really do not like them being the same size (especially when not all of the applets over by the system tray scale similarly--but I would still dislike them being so large if they were consistent).

        nolan just to be clear I was excited that the network manager applet notification was finally gone from Raven, not the taskbar. I should have been clearer. It had the wrong icon and didn't need to be there so I'm glad it disappeared.

            brent oh, you mean the notification, yea it was no pleasant to watch.
            I misunderstood your comment but I didn't get mad or anything else just a bit confused.

                nolan that was all on me. did not make myself clear at all. just shrieking in joy it was gone. thanks to whoever removed the unpleasantness🙂

                  Hello, just one problem: when I try to launche umbrello for UML, nothing happenes. I'm using Budgie. Except that, it's perfect! Thank you guys

                  Solarmass Silversurfer I have the same issue with my own Python based indicator app.

                  I created a short demo app which shows that specifying icons by full file path doesn't work anymore, while specifying an icon name from the icon pool works:

                  appindicator_demo.py

                      After this update my dell xps15 9560 freezes shortly after login.

                      I have tried reinstalling solus 4.4 budgie version with a complete wipe of the drive. Then it worked fine untill i updated and it's back to being unusable.

                      Please let me know what information I need to share to be able to debug.

                        c2p Green is the new blue, ok, which gtk-theme shall i use, to match the budgie-theme?

                        I still use Plata-noir-compact (don't use it, it's outdated) for the very dark header-bars.

                          hakimjonas When it freezes can you still switch to a TTY? If so do so and run sudo journalctl -b0 > frozen-login.log and then upload that to pastebin and post the link here. You may need to boot into a recovery USB in order to get the file from the hard drive.

                              Hey guys,

                              Thank you for bringing Solus back to life!
                              I have an issue with bluetooth on my desktop and I suspect this happened with the sync updates for week 32, since I was away from my computer for a couple of weeks. When I finally got home this Monday I sat to finish some work and updated several hours later. Till that time my bluetooth mouse was working just fine, but after updating (what was released for week 33) the connection stayed only for up to a minute after reboot and then the mouse stopped working. This behaviour lasted after 2-3 restarts, then I simply plugged the dongle out, put it back in place and removed the mouse as a device from the settings menu to try re-pair and connect it this way, but my computer does not see this device anymore. I have a bluetooth headset that is also not working anymore - cannot get it to connect with my PC. I have a Windows laptop (dual boot with Solus) with which my mouse still works just fine (haven't tried with Solus though).
                              Hopefully someone could help as all my attempts were like shots in the dark (sorry but my knowledge is limited) 🙁
                              Here is what systemctl gives me back, but please let me know if I need to provide anything else:

                              $ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: e
nabled)
    Drop-In: /usr/lib64/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sun 2023-08-27 20:56:47 EEST; 30min ago
       Docs: man:bluetoothd(8)
   Main PID: 664 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 16637)
     Memory: 2.8M
        CPU: 46ms
     CGroup: /system.slice/bluetooth.service
             └─664 /usr/lib64/bluez/bluetooth/bluetoothd

Aug 27 21:00:03 soluspc bluetoothd[664]: Failed to add UUID: Authentication Failed (0x05)
Aug 27 21:00:05 soluspc bluetoothd[664]: Failed to add UUID: Authentication Failed (0x05)
Aug 27 21:00:07 soluspc bluetoothd[664]: Failed to add UUID: Authentication Failed (0x05)
Aug 27 21:00:09 soluspc bluetoothd[664]: Failed to add UUID: Authentication Failed (0x05)
Aug 27 21:00:11 soluspc bluetoothd[664]: Failed to add UUID: Authentication Failed (0x05)
Aug 27 21:00:13 soluspc bluetoothd[664]: Failed to add UUID: Authentication Failed: (0x05)
Aug 27 21:00:15 soluspc bluetoothd[664]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Connection timed out
Aug 27 21:00:15 soluspc bluetoothd[664]: Failed to add UUID: Authentication Failed (0x05)
Aug 27 21:00:56 soluspc bluetoothd[664]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1A:7D:13:11:4A: Connection refused (111)
Aug 27 21:01:14 soluspc bluetoothd[664]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1A:7D:13:11:4A: Connection timed out (110)

                              I would like to apologize for the late notice and if this is not the correct thread!

                              Edit:
                              Just found a post on another distro's bug report page which states that bluetooth has not been working for them since kernel 6.4. As I see, there is a commit on git.kernel.org on July 13 that should probably fix the issue. As of now, I downloaded the lts-kernel and selected it upon boot - my bluetooth devices seem to be working just fine (for the last 15 mins or so).

                              ReillyBrogan No unfortunately I cannot. Even just opening the ternimal and writing a file like "touch x.txt" seems to have catastrophic results, like either a total freeze or immediate reboot. I have tried with and without nvidia drivers with the same result. I would love to think that PC was just broken but with a clean install i works. its only after the update this happens.

                                  hakimjonas well if you boot with the USB it should be possible to get the journal logs off of it using journalctl in the boot USB. Basically there's nothing we can do to help you figure this out without the logs, but the good news is they should still be written even when the system is unresponsive. I'm not in front of my computer rn so I can't give you the specific commands to use, but they should be possible to find with an internet search.

                                  Also, try the lts kernel. It may work instead since this sounds like it's most likely a kernel issue of some kind.

                                      penny-farthing , Salut, j'ai fait quelques corrections. N'hésitez pas à me les signaler "précisément", c'est plus facile ensuite de les corriger. Elles seront sans doute prises en compte lors de la prochaine version de Budgie.

                                      Hi, I have made some corrections. Don't hesitate to "precisely" point them out, it is then easier to correct. They will be taken into account with the publishing of the next Budgie version.

                                      Regards.

                                        Everyting went well
                                        I found out why I couldn't boot Gnome Wayland since previous sync: Pixel Saver extention. My bad...