Bug 504690

Summary: The bottom bar freezes constantly
Product: [Applications] kdeconnect Reporter: r.vacho
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andrew.g.r.holmes, cwo.kde, kde
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: syslog
journalctl -f

Description r.vacho 2025-05-23 08:40:13 UTC
Created attachment 181670 [details]
syslog

SOFTWARE/OS VERSIONS: Kubuntu 25.04
KDE Plasma Version: 6.3.x-6.4 beta
KDE Frameworks Version: 6.12-6.14
Qt Version: 6.8.3
Nvidia drivers: Nouveau, Nvidia (differents)

Maybe it was happening in Plasma 6.1 as well. We're not sure. Anyway, what I've observed is that this is currently happening to me after every system boot. Earlier, it only happened sometimes. The used graphics driver, either Nvidia or Nouveau, does not have any influence on it.
The system responds to mouse clicks on the panel and elsewhere during the freeze. Only some tasks related to the panel are executed after the unfreeze. ALT+TAB, for example, works even during the freeze. I can also minimize a window, but it cannot be maximized again. It might get maximized somewhere, but it's not visually apparent.
 The freezing lasts about 15-20 seconds. I need to measure it sometime. 

At one point, this phenomenon ceased to occur. Then I deleted the KDE configuration in /home and it started appearing regularly again after each Plasma startup.

Log timeline for an errors is 10:04-10:05.
Comment 1 r.vacho 2025-05-23 08:40:56 UTC
Created attachment 181671 [details]
journalctl -f
Comment 2 cwo 2025-05-25 10:36:36 UTC
Thank you for the bug report! From the logs, it seems like you are hitting a bug where KDE Connect's bluetooth backend cannot be activated  and this causes the system to freeze for a bit. There is a report about this open for KDE Connect, which I'm marking this a duplicate of. 

Please contribute any extra information you might have to that report - as I understand it there is currently no clear cause known.

*** This bug has been marked as a duplicate of bug 503431 ***
Comment 3 r.vacho 2025-05-25 10:42:49 UTC
It is likely. I turned off this backend and since then this incident has not happened to me.
Comment 4 Rob Emery 2025-06-07 15:09:48 UTC
(In reply to r.vacho from comment #3)
> It is likely. I turned off this backend and since then this incident has not
> happened to me.

Hiya,

Is this still reproducible on the latest version available through KUbuntu? If so, could you share some information about your hardware configuration, as well as 
```
sudo bluetoothctl list
sudo systemctl status bluetooth
find /sys/class/bluetooth/*/
```

Thanks,
Comment 5 Rob Emery 2025-06-27 18:07:50 UTC
Fix for underlying behaviour in https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/837