2218421 – bluetooth does not turn on after the laptop comes out of sleep mode

Bug 2218421 - bluetooth does not turn on after the laptop comes out of sleep mode

Summary: bluetooth does not turn on after the laptop comes out of sleep mode

Keywords:
Status:	NEW
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	gnome-bluetooth
Sub Component:
Version:	38
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	---
Assignee:	Bastien Nocera
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-06-29 05:28 UTC by Serge
Modified:	2023-06-29 05:29 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type:	---
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description Serge 2023-06-29 05:28:11 UTC

After the laptop comes out of sleep mode turning on the bluetooth button does not lead to results. The button is active in the settings, but when switching it immediately switches to the off state. Restarting bluetooth.service does not help. Reboot only.

Reproducible: Always

Steps to Reproduce:
1.Putting the laptop into sleep mode
2.Wake up the laptop from sleep mode
3.
Actual Results:  
Can't activate bluetooth


Fedora Linux 38 (Workstation Edition)
Gnome 44.2
Linux 6.3.8-200.fc38.x86_64

[   44.366867] Bluetooth: Core ver 2.22
[   44.367009] NET: Registered PF_BLUETOOTH protocol family
[   44.367021] Bluetooth: HCI device and connection manager initialized
[   44.367040] Bluetooth: HCI socket layer initialized
[   44.367053] Bluetooth: L2CAP socket layer initialized
[   44.367093] Bluetooth: SCO socket layer initialized
[   44.758625] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017
[   44.759561] Bluetooth: hci0: Device revision is 2
[   44.759596] Bluetooth: hci0: Secure boot is enabled
[   44.759605] Bluetooth: hci0: OTP lock is enabled
[   44.759613] Bluetooth: hci0: API lock is enabled
[   44.759621] Bluetooth: hci0: Debug lock is disabled
[   44.759629] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   45.138664] Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi
[   45.139088] Bluetooth: hci0: Boot Address: 0x24800
[   45.139107] Bluetooth: hci0: Firmware Version: 144-11.23
[   47.553076] Bluetooth: hci0: Waiting for firmware download to complete
[   47.553498] Bluetooth: hci0: Firmware loaded in 2358179 usecs
[   47.553689] Bluetooth: hci0: Waiting for device to boot
[   47.570628] Bluetooth: hci0: Device booted in 16614 usecs
[   47.570657] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[   47.574928] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-32-4.ddc
[   47.576641] Bluetooth: hci0: Applying Intel DDC parameters completed
[   47.577632] Bluetooth: hci0: Firmware revision 0.4 build 144 week 11 2023
[   48.706515] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   48.706537] Bluetooth: BNEP filters: protocol multicast
[   48.706560] Bluetooth: BNEP socket layer initialized
[   48.717600] Bluetooth: MGMT ver 1.22
[   50.700251] Bluetooth: RFCOMM TTY layer initialized
[   50.700261] Bluetooth: RFCOMM socket layer initialized
[   50.700265] Bluetooth: RFCOMM ver 1.11

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