Bug 515753 - Open Network tab causes Bluetooth to crash
Summary: Open Network tab causes Bluetooth to crash
Status: NEEDSINFO BACKTRACE
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.12.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-09 07:07 UTC by MorningMC
Modified: 2026-02-10 17:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MorningMC 2026-02-09 07:07:05 UTC
SUMMARY
Open Network tab in Dolphin causes Bluetooth to crash.
execute `systemctl --user mask obex` can solve this issue, but also disables dolphin to transfer files through Bluetooth.
Shutdown, wait for half a minute, then boot or hibernate, wait for half a minute, then resume can bring Bluetooth back, but does not stop Dolphin destroying Bluetooth.
Simply execute `systemctl restart bluetooth` does nothing.

STEPS TO REPRODUCE
1. Click Network in Places panel.

OBSERVED RESULT
Bluetooth crashed immediately when Network tab displays.

EXPECTED RESULT
Bluetooth is unaffected.

SOFTWARE/OS VERSIONS
Environment: Arch Linux (rolling)
Linux Kernel: Linux 6.18.8-zen2-1-zen (x86_64) - Page size 4.00 KiB
KDE Plasma Version: Not installed
Qt Version: 6.10.2-1
Dolphin Version: 25.12.2-1

ADDITIONAL INFORMATION
Output of `systemctl status bluetooth`:
```
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Mon 2026-02-09 14:15:30 CST; 28min ago
 Invocation: 345fcf2ea12f45fa9e137c6946c614d9
       Docs: man:bluetoothd(8)
   Main PID: 769 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37653)
     Memory: 3.1M (peak: 4.6M)
        CPU: 20ms
     CGroup: /system.slice/bluetooth.service
             └─769 /usr/lib/bluetooth/bluetoothd

Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/faststream
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/opus_05
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/opus_05
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Feb 09 14:17:10 MorningMC-ArchLinux bluetoothd[769]: Battery Provider Manager destroyed
```

Output of `sudo dmesg | grep -i "Bluetooth"`:
```
[    3.715445] Bluetooth: Core ver 2.22
[    3.715457] NET: Registered PF_BLUETOOTH protocol family
[    3.715458] Bluetooth: HCI device and connection manager initialized
[    3.715460] Bluetooth: HCI socket layer initialized
[    3.715462] Bluetooth: L2CAP socket layer initialized
[    3.715464] Bluetooth: SCO socket layer initialized
[    3.945049] Bluetooth: hci0: HW/SW Version: 0x00000000, Build Time: 20260106153314
[    4.749329] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.749332] Bluetooth: BNEP filters: protocol multicast
[    4.749336] Bluetooth: BNEP socket layer initialized
[    5.792208] Bluetooth: hci0: Device setup in 1805688 usecs
[    5.792215] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[    5.880355] Bluetooth: hci0: AOSP extensions version v1.00
[    5.880362] Bluetooth: hci0: AOSP quality report is supported
[    5.885405] Bluetooth: MGMT ver 1.23
[   21.393741] Bluetooth: RFCOMM TTY layer initialized
[   21.393747] Bluetooth: RFCOMM socket layer initialized
[   21.393749] Bluetooth: RFCOMM ver 1.11
[   58.936249] Bluetooth: hci0: HW/SW Version: 0x00000000, Build Time: 20260106153314
[   59.239902] Bluetooth: hci0: Device setup in 298017 usecs
[   59.239908] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   59.328687] Bluetooth: hci0: AOSP extensions version v1.00
[   59.328693] Bluetooth: hci0: AOSP quality report is supported
[  104.583885] Bluetooth: hci0: urb 00000000f41c8804 failed to resubmit (2)
```

Output of `bluetoothctl`:
```
Agent registered
[bluetoothctl]> list
[bluetoothctl]> power on
No default controller available
```

Output of Dolphin:
```
bluedevil.kio_bluetooth: Kio Bluetooth instanced!
bluedevil.kio_bluetooth: Setting host:  ""
bluedevil.kio_bluetooth: Stat:  QUrl("bluetooth:/")
bluedevil.kio_bluetooth: Stat:  QUrl("bluetooth:/")
bluedevil.kio_bluetooth: Stat:  QUrl("bluetooth:/")
bluedevil.kio_bluetooth: Stat:  QUrl("bluetooth:/")
bluedevil.kio_bluetooth: Stat:  QUrl("bluetooth:/")
```

Tried but failed solutions: 
1. write `options bluetooth disable_esco=1` to modprobe config
2. write `btusb.enable_autosuspend=n` to kernel parameters
3. execute `systemctl restart bluetooth`
4. execute `modprobe -r btusb; modprobe btusb`
...
Comment 1 TraceyC 2026-02-10 17:36:37 UTC
Thanks for the crash report. As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

Thanks.