Bug 497532 - Bluetooth adapter don't turn on
Summary: Bluetooth adapter don't turn on
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_bluetooth (show other bugs)
Version: 6.2.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-16 01:59 UTC by guga.4004
Modified: 2025-01-15 03:47 UTC (History)
2 users (show)

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

Attachments
Bluetooth options (13.82 KB, image/png)
2024-12-16 01:59 UTC, guga.4004 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description guga.4004 2024-12-16 01:59:59 UTC 
Created attachment 176668 [details]
Bluetooth options

i have recently installed Garuda KDE Dr460nized, and my bluetooth adapter detect but don't turn on, it keep saying bluetooth is disabled
Comment 1 Nate Graham 2024-12-16 18:25:53 UTC 
Sorry, what's the bug here? You'd like for the Bluetooth adapter to be turned on at login, and this isn't happening?

If so, there are a few ways to do this:
1. Turn it on now. It's supposed to remember on the next login. If it's not, there's something going wrong somewhere
2. System Settings > Bluetooth > Turn on > "Configure…" > "On Login: Enable Bluetooth"
3. Use a distro package or firmware setting (if applicable; will depend on your hardware and distro) to turn on Bluetooth on boot
Comment 2 Bug Janitor Service 2024-12-31 03:47:25 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-01-15 03:47:52 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.