Week 20, 2026

DinimixisDEMZ

All's ok in Solus GNOME. Thank's!!

Bipolar_Bear

All fine here, bluetooth also working but then again I have USB dongle on my desktop…this kernel update could most likely only be affecting laptops and some desktops with those wifi/bluetooth chipsets on motherboards.

But yeah, thank you once again Solus team! 🙂

penny-farthing

84 packages updated today in Solus Budgie and nothing to report since.
Bluetooth operational.

Congratulations to Solus team.

Jaredy899

nodejs-24 is now in the repo. With that, it means pnpm is updated and is now built from nodejs-24.

craigtoyoracer

Harvey All good here on Budgie, I know it was only 60 pkg.s but 1 min. 30 sec. start to finish is " Sic man "

about those "pickles" are they dill, gherkin. bread and butter. 🙂 never heard the term before.

Axios

Budgie and Plasma all ok.

totalmongobaer

It was an easy update for Gnome on AMD , a perfect Distro for me, thank you!

Solarmass

report from Budgie Wayland: it boots, no problem

VTMarik

Izanagi How does one ascertain an ETA if there is one?

Izanagi

VTMarik It probably will be included in the next kernel version. 7.0.8 is already out. I haven't checked if it has the fix but if not, 7.0.9 should have it, I think.

Julien68

Hello, I'm having the same issue with Bluetooth as well, while I wait for the fix in the next kernel.

[    7.882390] Bluetooth: Core ver 2.22
[    7.882404] NET: Registered PF_BLUETOOTH protocol family
[    7.882405] Bluetooth: HCI device and connection manager initialized
[    7.882408] Bluetooth: HCI socket layer initialized
[    7.882410] Bluetooth: L2CAP socket layer initialized
[    7.882413] Bluetooth: SCO socket layer initialized
[    7.961501] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20260224103448
[    8.101393] Bluetooth: hci0: Failed to send wmt func ctrl (-22)
[    8.101397] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[    8.687592] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    8.687595] Bluetooth: BNEP filters: protocol multicast
[    8.687598] Bluetooth: BNEP socket layer initialized

Julien68

In the meantime, I edited the loader.conf file so that it boots using the previous kernel.

Harvey

Izanagi

This was helpful thank you. I am building 7.0.8 with that patch now (Not in 7.0.8 proper). But it will not be on polaris (stable) until next sync.

majunia28

Guys, since 7.0.3 the Display manager refuse to work on a Solus Budgie laptop.
Im using an all AMD CPU/GPU. The last working kernel is 6.18.23-334. eopkg history show me that i have nvidia-driver-470 and glx installed (I dont know why this happens, but remove it from my machine and reboot into 6.18,23-334). The laptop boot and works well this way, but if I update to a new kernel the display manager fails

If I type on a terminal sudo clr-boot-manager list-kernels the return looks like this
* com.solus-project.current.7.0.7-339

com.solus-project.current.6.18.23-334

Booting into 7.0.7 gives me the black screen with cursor but I can get into TTY with ctrl+alt+F2 and run
sudo eopkg check (no issues)
sudo eopkg up -y (no issues)

LTS is the only solution?

Harvey

majunia28 Im using an all AMD CPU/GPU.

If you do not have an nvidia GPU you should not have nvidia drivers installed.

eopkg li | grep nvidia

If it shows *-modaliases packages that is fine but if you have stuff like:

nvidia-glx-driver* or nvidia-470-glx-driver* etc without -modaliases in the name. You should remove them.

brent

majunia28 Guys, since 7.0.3 the Display manager refuse to work on a Solus Budgie laptop.

sudo systemctl status lightdm

● lightdm.service - Light Display Manager

Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)

Active: active (running) since Sat 2026-05-16 12:20:41 MST; 7h ago

Should say enabled and running.

Now the mystery is this: why/how could the current kernel break the Display Manager? Find the answer to that and it's solved. Unless there's too many variables? We ruled out Nvidia.

Sometimes on Budgie certain applets added to the task bar will break Budgie/LightDM. This is true for X11 and Wayland versions. Which could be a Budgie thing and not necessarily kernel.

Never used LTS so I don't know why everything works with it so I can't comment there.

Trying to steer you to more troubleshooting/wish I knew the answer. Hang in there, you have a hiccup with something.

pcdery

majunia28 same thing for me, laptop with amd, no gpu, no problems with LTS, but black screen (no login screen) with 7.0.7

majunia28

Harvey

eopkg history shows that I removed this 2 packages

nvidia-470-glx-driver-modaliases 470.256.02-139-1-x86_64 is removed

nvidia-glx-driver-modaliases 580.159.03-603-1-x86_64 is removed

eopkg li | grep nvidia

returns nothing

Harvey

majunia28

The modaliases packages are used for hardware detection, they are not drivers. But they don't need to be installed by default any more so the fact you removed them is fine.

I am curious if the kernel image actually installed properly.
sudo clr-boot-manager mount-boot

An then provide the output of:
df -h /boot/

majunia28

Harvey

sudo clr-boot-manager mount-boot

Returns nothing

df -h /boot/

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 1022M 228M 795M 23% /boot

Harvey

majunia28

Yeah the first command just made sure /boot was mounted otherwise the next command I got you to run would've returned the drive usage for the root ( / ) partition instead of /boot so returning nothing is normal.

Unfortunately I'm out of idea, considering sudo eopkg check returns no issues, there is plenty of space in /boot and no actual nvidia drivers were installed.

Sorry. Hopefully someone else has an idea.

majunia28

Harvey

Thanks dude, I appreciate the time you dedicated to help me. I ll keep digging into this.

« Previous Page Next Page »