[SOLVED] Plasma Desktop takes ages to startup: any hint?

0BADC0DE · 2024-03-15 08:55:05

seth wrote:

The bug is actually specifically because kdeconnect cannot contact bluez, whether that's because you don't have bluetooth, don't have it enabled or don't have bluez installed or have it masked.

Not really. I have full BT support also in KDE.
The only thing I have is the system tray: I have a "shown when relevant".
If I put it as "Always" I can see BT is enabled and I can connect devices...
Let me try with "Always shown" and ksplash unmasked.

seth · 2024-03-15 08:59:17

Check whether bluez then shows up anywhere in your journal resp. whether the service exists and is active,

systemctl status bluetooth.service

There's an optional dependency chain, /me wonders whether you're maybe resolving that through the qt5 path…

0BADC0DE · 2024-03-15 09:52:48

seth wrote:

Check whether bluez then shows up anywhere in your journal resp. whether the service exists and is active,
systemctl status bluetooth.service
There's an optional dependency chain, /me wonders whether you're maybe resolving that through the qt5 path…

I checked despite I knew the answer.
It has been enabled and active since ... ever.
My very own installation script does that.
Having BT enabled or not seems not making any difference here.

Last edited by 0BADC0DE (2024-03-15 09:53:15)

Arch Linux

#26 2024-03-15 08:55:05

Re: [SOLVED] Plasma Desktop takes ages to startup: any hint?

#27 2024-03-15 08:59:17

Re: [SOLVED] Plasma Desktop takes ages to startup: any hint?

#28 2024-03-15 09:52:48

Re: [SOLVED] Plasma Desktop takes ages to startup: any hint?

Board footer