Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1815635

Summary: Fedora 31 bluetooth stopped working
Product: [Retired] Fedora Documentation Reporter: super250
Component: technical-notesAssignee: Petr Bokoc <pbokoc>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: develCC: wb8rcr, zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 09:23:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description super250 2020-03-20 19:06:25 UTC
Description of problem: bluetooth stopped working

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


How reproducible:


Steps to Reproduce:
1.\<edit\> /usr/lib/systemd/system/bluetooth.service
  \<add '-d' to ExecStart line as option to bluetoothd\>

2. systemctl daemon-reload

3. systemctl restart bluetooth

(Capture the logs to put in bugzilla report) journalctl -r -u bluetooth > /tmp/bluetoothd.out

Actual results:

bluetooth.service: Service has
 no ExecStart=, ExecStop=, or SuccessAction=. Refusing


Expected results:

bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2017-10-04 16:07:40 EDT; 1 day 22h ago
     Docs: man:bluetoothd(8)
 Main PID: 27427 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─27427 /usr/libexec/bluetooth/bluetoothd

Additional info:

Comment 1 Petr Bokoc 2024-05-21 09:23:37 UTC
This guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.