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.
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.
ReillyBrogan ill try it tomorrow thank you
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...
Hi, thanks for the awesome update!
Am I the only one suffering from keyboard focus issues ?
What I mean is that can't just type in Ulauncher or guake after pressing the shortcut to visualize them.
Instead now I have to focus the application, which is counter productive
Anyone else having the same problems ?
EDIT: SOLVED by reinstalling the problematic apps and rebooting the OS.
Cheers,
PY
JoshStrobl The one app that I noticed this on was VeraCrypt. Normally there's an icon in the tray but there isn't. When I go to open the app again, I get a "VeraCrypt is already running" message.
Today this problem appeared with digikam on Budgie Solus, i don't know if it is related with the latest update:
~ $ digikam
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: cannot register existing type 'GdkDisplayManager'
(digikam:49628): GLib-CRITICAL **: 22:38:28.301: g_once_init_leave: assertion 'result != 0' failed
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: invalid (NULL) pointer instance
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: invalid (NULL) pointer instance
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.306: cannot register existing type 'GdkDisplay'
(digikam:49628): GLib-CRITICAL **: 22:38:28.306: g_once_init_leave: assertion 'result != 0' failed
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.306: g_type_register_static: assertion 'parent_type > 0' failed
(digikam:49628): GLib-CRITICAL **: 22:38:28.306: g_once_init_leave: assertion 'result != 0' failed
(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.306: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
Errore di segmentazione (core dump creato)Anyone else having the same problem?
Discord update has been cherrypicked to shannon. Update again.
So unfortunately I have not been able to produce a log. But what I have done is reinstalled 4.4, switched to the lts-kernel and then done the system update. This turns out the same, which leads we to think that the issue is not a kernel issue. At least not solely. And as long as I dont update, the system works fine, which suggest that its not just a hardware issue either.
I did see some chatter in the arch forums about the 6.4.11 kernel and even an issue related to the SD card reader but for me following the steps there to blacklist the device did not help either and in that case using the lts kernel should also have helped. I'll see if it is at all possible to get a log of what is happening.
Does anyone else have issues with brave browser? Sites keep crashing, and browser itself keeps crashing.
mbevks , same for me.
Also the tray icon for this nice widget - https://github.com/tsmetana/spotify-tray just disappeared.
The try icon for one obsolete application (gnome-pie) is now visible all the time, no matter that app is configured to disable the panel icon.
hakimjonas the next sync will include kernel 6.4.13 so hopefully that helps. But really a log is the most useful thing that you could provide.
