AlphaElwedritsch My V4 Bluetooth mouse stopped directly after the update so the only equipment unaffected is V3 or earlier.
Solus Updates for Week 12, 2025
- Edited
At home I found an old small bluetooth mouse 'GENIUS' with a large bluetooth antenna, inserted batteries into it and after several manipulations connected it to Solus 4.7 What is curious is that bluetooth does not see the name of the mouse, He does not know its name! I assume it has Bluetooth version 3
The mouse works, but on my Acer laptop it is unusual to see a large Bluetooth antenna intended for PC system units
@WetGeek as I remember, you have a lot of Bluetooth devices. Have you any problems with your devices since the last sync update?
minh
Thanks for the heads up, I'm on Budgie with an NVME boot drive & Nvidia gfx card. So I did a test, I installed all updates apart from the x4 Nvidia packages. Rebooted & everything was fine...then I thought I'd 'risk it for a biscuit' & installed the x4 Nvidia packages & it borked to that same recurring error message you have. I didn't have any extra kernels installed, so I had to live usb chroot & rolled backed to before x4 Nvidia packages when all good.
So No Visual Interface Display Is Accessible - the way it's meant to be..?
Same issue than 2 weeks ago, previous fallback kernel did not remove itself, had to clear it manually for the new one to install correctly. Is editing the EFI partition size safe to do ? 
BuzzPCSOS Fixed on unstable. Try this. sudo eopkg it https://cdn.getsol.us/repo/unstable/b/bluez/bluez-5.80-58-1-x86_64.eopkg
ReillyBrogan Thank you for the swift response. Unfortunately that fix did not work for me. I can still connect Bluetooth V3 devices but V4 devices fail to connect.
BuzzPCSOS same for me. I mentioned this already yesterday in the issue on git. Maybe this fix fixes something but unfortunately not everything.
@ReillyBrogan added a newer version 5.80-59
I will test it tomorrow
https://github.com/getsolus/packages/issues/5268#issuecomment-2759111272
sudo eopkg it https://cdn.getsol.us/repo/unstable/b/bluez/bluez-5.80-59-1-x86_64.eopkg
cannot be installed.
bluez-5.80-59-1-x86_64.eopkg [cached]
System error. Program terminated.
External dependencies not satisfied: libical release >= 21
Yeah the patched bluez was built against a newer version of libical than exists in shannon (stable) repo. So its not as simple to install, might as well wait for sync at this point.
Harvey might as well wait for sync at this point.
That was exactly my thought. Especially because the sync is already due in a few hours.
So why bend the whole system 
EbonJaeger unstickied the discussion .