Bug 456292 - Need to activate Bluetooth twice to turn it on
Summary: Need to activate Bluetooth twice to turn it on
Status: RESOLVED WORKSFORME
Alias: None
Product: Bluedevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.25.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-03 19:39 UTC by popov895
Modified: 2022-07-06 17:37 UTC (History)
3 users (show)

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


Attachments
Bluetooth applet (67.03 KB, image/png)
2022-07-03 19:39 UTC, popov895
Details

Note You need to log in before you can comment on or make changes to this bug.
Description popov895 2022-07-03 19:39:02 UTC
Created attachment 150371 [details]
Bluetooth applet

SUMMARY

Currently I need to do two things to activate Bluetooth.

In the Bluetooth applet:
1. Click the "Enable" button in the middle of it
2. Check the "Enable Bluetooth" checkbox in the header

In the Bluetooth KCM:
1. Click the "Enable" button in the middle of it
2. Click the "Enable" button in the middle of it again

The second point seems redundant to me, one action should be enough to activate Bluetooth. This is how it's implemented in Gnome and, it seems, in Windows.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20220701
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Graphics Platform: X11
Comment 1 Nate Graham 2022-07-05 17:47:43 UTC
Works for me. If you wait for 50 or 10 seconds after clicking the first thing, does everything work?
Comment 2 Nate Graham 2022-07-05 17:53:45 UTC
Does the problem goes away when TLP is disabled?
Comment 3 popov895 2022-07-05 18:54:25 UTC
(In reply to Nate Graham from comment #1)
> If you wait for 50 or 10 seconds after clicking the first
> thing, does everything work?
No.

(In reply to Nate Graham from comment #2)
> Does the problem goes away when TLP is disabled?
No.
Comment 4 Nate Graham 2022-07-06 15:16:13 UTC
Weird.
Comment 5 popov895 2022-07-06 17:37:03 UTC
Just checked, there is no such problem on a live image, so it looks like it's just me.