Bug 1163626 - Bluetooth not working after last update (kernel 5.2.2-1)
Summary: Bluetooth not working after last update (kernel 5.2.2-1)
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-14 01:29 UTC by Igor Kuznetsov
Modified: 2020-02-18 04:55 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Kuznetsov 2020-02-14 01:29:54 UTC
uname -a
Linux lnxvrxtosh 5.5.2-1-default #1 SMP Sat Feb 8 07:54:02 UTC 2020 (994cf1f) x86_64 x86_64 x86_64 GNU/Linux

[bluetooth]# list
Controller E4:F8:9C:52:F8:4A lnxvrxtosh [default]
[bluetooth]# devices
[bluetooth]# exit

in journalctl have no errors about bluetooth
Comment 1 Vitaly Korotkov 2020-02-14 07:53:21 UTC
Same problem on Tumbleweed.
Comment 2 Igor Kuznetsov 2020-02-18 04:55:06 UTC
Very strange...

[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[CHG] Controller E4:F8:9C:52:F8:4A DiscoverableTimeout: 0x00000000
[CHG] Controller E4:F8:9C:52:F8:4A DiscoverableTimeout: 0x00000000
[CHG] Controller E4:F8:9C:52:F8:4A DiscoverableTimeout: 0x00000000
[CHG] Controller E4:F8:9C:52:F8:4A DiscoverableTimeout: 0x00000000
[CHG] Controller E4:F8:9C:52:F8:4A DiscoverableTimeout: 0x00000000

bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Mon 2020-02-17 20:09:35 +04; 1h 26min ago
       Docs: man:bluetoothd(8)
   Main PID: 1561 (bluetoothd)
      Tasks: 1 (limit: 4915)
     Memory: 2.7M
     CGroup: /system.slice/bluetooth.service
             └─1561 /usr/lib/bluetooth/bluetoothd

фев 17 20:10:37 lnxvrxtosh bluetoothd[1561]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc
фев 17 20:13:30 lnxvrxtosh bluetoothd[1561]: Endpoint unregistered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc
фев 17 20:13:30 lnxvrxtosh bluetoothd[1561]: Endpoint unregistered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc
фев 17 20:29:31 lnxvrxtosh bluetoothd[1561]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc
фев 17 20:29:31 lnxvrxtosh bluetoothd[1561]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc
фев 17 20:29:57 lnxvrxtosh bluetoothd[1561]: Failed to set mode: Blocked through rfkill (0x12)
фев 17 21:12:39 lnxvrxtosh bluetoothd[1561]: Endpoint unregistered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc
фев 17 21:12:39 lnxvrxtosh bluetoothd[1561]: Endpoint unregistered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc
фев 17 21:34:02 lnxvrxtosh bluetoothd[1561]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc
фев 17 21:34:02 lnxvrxtosh bluetoothd[1561]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc

lnxvrxtosh:/home/virex # rfkill 
ID TYPE      DEVICE                 SOFT      HARD
 0 bluetooth Toshiba Bluetooth unblocked unblocked
 1 wlan      phy0              unblocked unblocked
 4 bluetooth hci0                blocked unblocked
lnxvrxtosh:/home/virex # rfkill unblock 4
lnxvrxtosh:/home/virex # rfkill 
ID TYPE      DEVICE                 SOFT      HARD
 0 bluetooth Toshiba Bluetooth unblocked unblocked
 1 wlan      phy0              unblocked unblocked
 4 bluetooth hci0              unblocked unblocked
lnxvrxtosh:/home/virex #

trying to on, but it is switch to another number 

rfkill 
ID TYPE      DEVICE                 SOFT      HARD
 0 bluetooth Toshiba Bluetooth unblocked unblocked
 1 wlan      phy0              unblocked unblocked
 8 bluetooth hci0                blocked unblocked

but after several reboot it is start to work normal.