Bug 2157179 - Bluetooth was skipped because of a failed condition check
Summary: Bluetooth was skipped because of a failed condition check
Keywords:
Status: CLOSED DUPLICATE of bug 2153384
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 37
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Gopal krishna tiwari
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-31 16:42 UTC by jedrek
Modified: 2023-08-25 16:34 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-08-25 16:34:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description jedrek 2022-12-31 16:42:15 UTC
Description of problem:
This is serious. After 3 weeks of inactivity on my fresh Fedora 37 install my bluetooth no longer works. I can’t connect my wireless keyboard to do my work. I googled it and found some answers on Ask Fedora suggesting to do dnf upgrade which I did but bluetooth still doesn’t work. 

systemctl status bluetooth
Inactive(dead) Bluetooth was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth)

I didn’t do anything, it just stopped working. After 3 weeks of inactivity suddenly bluetooth stops working?

dmesg | grep bluetooth
Returns nothing.

It used to work just fine and it suddenly stoped working by itself.

lsmod
doesn’t return anything related to bluetooth.

Version-Release number of selected component (if applicable):
Fedora 37

systemctl enable bluetooth
systemctl start bluetooth
Reboot
Still doesn't work

How reproducible:


Steps to Reproduce:
1. Power up your computer
2. Check bluetooth

Actual results:
Bluetooth doesn't work

Expected results:
Bluetooth works and external devices can be connected.

Additional info:

Comment 1 Knut J BJuland 2023-02-18 17:20:33 UTC
Duplicate of 2153384

Comment 2 Peter Robinson 2023-08-25 16:34:15 UTC

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


Note You need to log in before you can comment on or make changes to this bug.