[ISSUE] Bluez crashes randomly, scan is empty

[ISSUE] Bluez crashes randomly, scan is empty

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

New issue by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52732

Description:
### Is this a new report?

Yes

### System Info

Void 6.11.4_1 x86_64 AuthenticAMD uptodate FFFFFF

### Package(s) Affected

bluez-5.76_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

N.A

### Expected behaviour

`scan on` should display the available bluetooth devices


### Actual behaviour

```
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan off
[bluetooth]# Failed to stop discovery: org.bluez.Error.Failed
```

### Steps to reproduce

1. bluetoothctl
2. scan on

Re: Bluez crashes randomly, scan is empty

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 242 bytes --]

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52732#issuecomment-2428344143

Comment:
yesterday it worked normally, but i guess another update randomly broke it for some reasons...

Re: Bluez looses control after scan, bluetooth somehow become a zombie process

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 2435 bytes --]

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52732#issuecomment-2430210590

Comment:
I tried running btmon like the archwiki suggest, in a desperate attempt to get more info:

```
Bluetooth monitor ver 5.76
btmon[11524]: = Note: Linux version 6.11.4_1 (x86_64)                                                                                                                                0.537217
btmon[11524]: = Note: Bluetooth subsystem version 2.22                                                                                                                               0.537221
= New Index: E0:0A:F6:73:7B:8E (Primary,USB,hci0)                                                                                                                             [hci0] 0.537223
= Open Index: E0:0A:F6:73:7B:8E                                                                                                                                               [hci0] 0.537224
= Index Info: E0:0A:F6:73:7B:8E (Realtek Semiconductor Corporation)                                                                                                           [hci0] 0.537225
bluetoothd[893]: @ MGMT Open: bluetoothd (privileged) version 1.23                                                                                                          {0x0001} 0.537227

bluetoothctl[11542]: @ MGMT Open: bluetoothctl version 1.23                                                                                                                {0x0002} 11.759877
bluetoothd[893]: @ MGMT Command: Start Discovery (0x0023) plen 1                                                                                                    {0x0001} [hci0] 13.237297
        Address type: 0x07
          BR/EDR
          LE Public
          LE Random
@ MGMT Event: Command Complete (0x0001) plen 4                                                                                                                      {0x0001} [hci0] 13.237313
      Start Discovery (0x0023) plen 1
        Status: Busy (0x0a)
        Address type: 0x07
          BR/EDR
          LE Public
          LE Random
bluetoothctl[11542]: @ MGMT Close: bluetoothctl                                                                                                                            {0x0002} 30.328488
```

Re: Bluez looses control after scan, bluetooth somehow become a zombie process

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 427 bytes --]

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52732#issuecomment-2430213666

Comment:
It's weird, because it works on my desktop, but not on my laptop. Despite the both of them having similar configurations.

I noticed as well that Bluez only detects *some* devices (My smart tv for example) but not other devices such as my bluetooth mouse.

It's really weird.

Re: btusb kernel module broken with some bluetooth chips since kernel 6.11.4_1

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 213 bytes --]

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52732#issuecomment-2431065136

Comment:
I can confirm, a rollback to 6.11.3_2 completely fixes the issue.

Re: btusb kernel module broken with some bluetooth chips since kernel 6.11.4_1

[dataCobra]

[-- Attachment #1: Type: text/plain, Size: 253 bytes --]

New comment by dataCobra on void-packages repository

https://github.com/void-linux/void-packages/issues/52732#issuecomment-2448020749

Comment:
Hey, this is a known issue of upstream and not an Void issue.

6.11.5 is out and fixes the bluetooth issue.

Re: [ISSUE] [CLOSED] btusb kernel module broken with some bluetooth chips since kernel 6.11.4_1

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

Closed issue by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52732

Description:
### Is this a new report?

Yes

### System Info

Void 6.11.4_1 x86_64 AuthenticAMD uptodate FFFFFF

### Package(s) Affected

bluez-5.76_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

N.A

### Expected behaviour

`scan on` should display the available bluetooth devices


### Actual behaviour

```
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan off
[bluetooth]# Failed to stop discovery: org.bluez.Error.Failed
```

### Steps to reproduce

1. bluetoothctl
2. scan on

Re: btusb kernel module broken with some bluetooth chips since kernel 6.11.4_1

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 171 bytes --]

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/52732#issuecomment-2448468619

Comment:
Can confirm it's fixed!