Bug 504098 - On connecting: Info label says wrongly "Disconnecting" shortly
Summary: On connecting: Info label says wrongly "Disconnecting" shortly
Status: RESOLVED DUPLICATE of bug 493245
Alias: None
Product: plasmashell
Classification: Plasma
Component: Bluetooth widget (other bugs)
Version First Reported In: 6.3.5
Platform: Other Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-12 13:11 UTC by postix
Modified: 2025-05-13 20:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot (406.14 KB, image/png)
2025-05-12 13:11 UTC, postix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2025-05-12 13:11:22 UTC
Created attachment 181212 [details]
Screenshot

Upon connecting a paired Bluetooth device by clicking on "Connect", the gray info labels first reads correctly "Connecting". When device is moved to the top in the list, the label changes shortly to "Disconnecting", until the device is actually connected.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250509
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.5-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 Nate Graham 2025-05-13 19:02:49 UTC
I can't reproduce this on Fedora 42 KDE with Linux kernel 6.14.5 and everything KDE built from source.
Comment 2 cwo 2025-05-13 20:31:13 UTC
I can reproduce this and filed it a couple of months ago.

If I remember correctly what I found then, there's a period where the applet is switching states, and briefly ends up in a state where it's already connected but still displaying the "working" string, which at that point then evaluates to "disconnecting".

One key thing for reproducing it is making the connection process take longer. Having a slow computer helps, but one key thing is to start fresh, either from a reboot or suspend/resume. It's not noticeable if you just disconnect and reconnect.

*** This bug has been marked as a duplicate of bug 493245 ***