Bluetooth Service needs to be restarted to work

Hello,

I’ve been experiencing issues when connecting my Soundcore Life Q30 wireless headphones to my laptop recently. I already tested them on other devices, my phone and another computer, but it’s still only happening on my laptop with Fedora. Whenever I turn them on and it begins to attempt pairing, it connects to the laptop, but then disconnects after 3 seconds. I tried uninstalling and installing bluez, forgetting the device in my bluetooth settings and hard resetting the headphones by holding the + and Power button for 5 seconds, but the only thing that fixes the issue is doing sudo systemctl restart bluetooth.service

Not just that, but last night, I reinstalled my Fedora OS completely, started brand new again. The headphones would pair completely fine, but, after installing all my apps, my gnome extensions, and then the most recent updates, it’s broken again, and I am not sure what exactly it could’ve been, it’s probably one of the most recent updates, one that happened within 1 or 2 weeks ago, no more.

Here are some logs regarding the service, but not sure how helpful they can be:

bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Mon 2025-06-23 04:49:05 CST; 10h ago
 Invocation: 0cd4b4c0fefb49c09730d86def809f89
       Docs: man:bluetoothd(8)
   Main PID: 893 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18873)
     Memory: 2.8M (peak: 3.8M)
        CPU: 177ms
     CGroup: /system.slice/bluetooth.service
             └─893 /usr/libexec/bluetooth/bluetoothd

Jun 23 04:50:02 Cerebro bluetoothd[893]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jun 23 04:54:31 Cerebro bluetoothd[893]: /org/bluez/hci0/dev_98_47_44_F4_B9_A2/fd0: fd(40) ready
Jun 23 07:41:32 Cerebro bluetoothd[893]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Jun 23 15:03:29 Cerebro bluetoothd[893]: No matching connection for device
Jun 23 15:04:19 Cerebro bluetoothd[893]: /org/bluez/hci0/dev_98_47_44_F4_B9_A2/sep2/fd4: fd(42) ready
Jun 23 15:04:22 Cerebro bluetoothd[893]: Failed to disconnect device: Disconnected (0x0e)
Jun 23 15:06:13 Cerebro bluetoothd[893]: src/profile.c:ext_auth() Hands-Free Voice gateway rejected 98:47:44:F4:B9:A2: org.bluez.Error.Canceled
Jun 23 15:06:15 Cerebro bluetoothd[893]: profiles/audio/avctp.c:avctp_connect_cb() connect to 98:47:44:F4:B9:A2: Software caused connection abort (103)
Jun 23 15:06:15 Cerebro bluetoothd[893]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Software caused connection abort
Jun 23 15:06:15 Cerebro bluetoothd[893]: No matching connection for device

caferino@Cerebro:~$ sudo systemctl restart bluetooth.service
caferino@Cerebro:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Mon 2025-06-23 15:08:18 CST; 15s ago
 Invocation: 5ab5d3105cf24908a349e399c1ca8741
       Docs: man:bluetoothd(8)
   Main PID: 31954 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18873)
     Memory: 1M (peak: 3.5M)
        CPU: 58ms
     CGroup: /system.slice/bluetooth.service
             └─31954 /usr/libexec/bluetooth/bluetoothd

Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/opus_g
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/sbc
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/sbc
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/faststream
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/opus_05
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/opus_05
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jun 23 15:08:18 Cerebro bluetoothd[31954]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jun 23 15:08:27 Cerebro bluetoothd[31954]: /org/bluez/hci0/dev_98_47_44_F4_B9_A2/sep2/fd0: fd(42) ready

My fastfetch:

User: caferino@Cerebro
OS: Fedora Linux 42 (Workstation Edition) x86_64
Host: HP ENVY m7 Notebook
Kernel: Linux 6.14.11-300.fc42.x86_64
Shell: bash 5.2.37
Display 1: 1280x720 @ 60 Hz, 17" (Built-in)
Display 2: 1920x1080 @ 60 Hz, 55" (Samsung External)
DE: GNOME 48.2
WM: Mutter (Wayland)
Terminal: Ptyxis 48.4
CPU: Intel Core i7-7500U (4) @ 3.50 GHz
GPU 1 (Discrete): NVIDIA GeForce 940MX
GPU 2 (Integrated): Intel HD Graphics 620 @ 1.05 GHz

My gnome extensions, which I disabled and tried, and still wouldn’t work:

  1. AppIndicator and KStatusNotifierItem Support
  2. Dash to Dock
  3. Disable Unredirect
  4. Extension List
  5. Hide Top Bar
  6. User Themes
  7. Vitals

The bluetooth was working fine right when the Fedora install was fresh, but it seems that, after around 30 updates, and then another 9 I installed in Software, the problem popped up, along another unrelated little glitch like invisible wayland windows that won’t let me click the “x” in some of my Brave tabs right now, one error that was reported as critical like 3 weeks ago.

I just discovered this one, I just woke up this morning. This invisible window issue would happen before every morning, I have 2 monitors, and I usually close the lid of my laptop to suspend it and use only the monitor to watch a show or video to fall asleep with, and I also use KDE Connect to control the cursor with my phone. I discovered that I have to close the KDE Connect sessions on the top bar to remove glitches of not being able to click anything, but right now, that did not fix it, and it’s only happening to two tabs in Brave depending on their position, like, there is a invisible window preventing clicks inputs between the two monitors at the top, it’s weird. Also tried disabling all the extensions and it’s still broken.


There’s also another tiny glitch where, KDE Connect won’t connect/work with my phone unless I run

killall kdeconnectd
kdeconnectd &

which is minor, but it’s there since Fedora 42 rolled out, it wouldn’t happen in 41 or earlier to me. It’s been like this for months, so, not sure how to pinpoint that issue.


Is there any way to fetch the most recent installed updates? All the dnf logs in my /var/log are way too long, there are like 5 text files of them, about 3 thousand lines each, only if they could be helpful though.

I also started having this issue on Fedora 42, more specifically i tested on Gnome version and my bluetooth works without any issue, but on the KDE version the only solution i found was restarting the bluetooth service after login.

I saw this on journalctl when i try to connect my headphones:

jun 26 13:49:40 fedora-loq systemd[2285]: Reached target bluetooth.target - Bluetooth.
jun 26 13:49:42 fedora-loq kded6[10034]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:49:42 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:49:42 fedora-loq kded6[10034]: org.kde.pulseaudio: No object for name "bluez_output.41_AA_00_CD_00_77.1"
jun 26 13:49:42 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_output.41_AA_00_CD_00_77.1"
jun 26 13:49:42 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:49:47 fedora-loq chronyd[1470]: Selected source 143.107.229.211 (2.fedora.pool.ntp.org)
jun 26 13:50:00 fedora-loq kernel: input: Baseus Bowie H1 Pro (AVRCP) as /devices/virtual/input/input31
jun 26 13:50:00 fedora-loq systemd-logind[1490]: Watching system buttons on /dev/input/event4 (Baseus Bowie H1 Pro (AVRCP))
jun 26 13:50:05 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:50:05 fedora-loq kded6[10034]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:50:05 fedora-loq kded6[10034]: org.kde.pulseaudio: No object for name "bluez_output.41_AA_00_CD_00_77.1"
jun 26 13:50:05 fedora-loq kded6[10034]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:50:05 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_output.41_AA_00_CD_00_77.1"
jun 26 13:50:05 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:50:18 fedora-loq kernel: input: Baseus Bowie H1 Pro (AVRCP) as /devices/virtual/input/input32
jun 26 13:50:18 fedora-loq systemd-logind[1490]: Watching system buttons on /dev/input/event4 (Baseus Bowie H1 Pro (AVRCP))
jun 26 13:50:23 fedora-loq kded6[10034]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:50:23 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"
jun 26 13:50:23 fedora-loq kded6[10034]: org.kde.pulseaudio: No object for name "bluez_output.41_AA_00_CD_00_77.1"
jun 26 13:50:23 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_output.41_AA_00_CD_00_77.1"
jun 26 13:50:23 fedora-loq plasmashell[10080]: org.kde.pulseaudio: No object for name "bluez_input.41:AA:00:CD:00:77"

This is my system:

System:
  Kernel: 6.15.3-200.fc42.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.4.0 Distro: Fedora Linux 42 (KDE Plasma Desktop
    Edition)
Machine:
  Type: Laptop System: LENOVO product: 83EU v: LOQ 15IRH8
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: No DPK serial: <superuser required>
    UEFI: LENOVO v: LZCN36WW date: 06/06/2024
Battery:
  ID-1: BAT1 charge: 37.4 Wh (64.6%) condition: 57.9/60.0 Wh (96.4%)
CPU:
  Info: 8-core (4-mt/4-st) model: 12th Gen Intel Core i5-12450H bits: 64
    type: MST AMCP cache: L2: 7 MiB
  Speed (MHz): avg: 960 min/max: 400/4400:3300 cores: 1: 960 2: 960 3: 960
    4: 960 5: 960 6: 960 7: 960 8: 960 9: 960 10: 960 11: 960 12: 960
Graphics:
  Device-1: Intel Alder Lake-P GT1 [UHD Graphics] driver: i915 v: kernel
  Device-2: NVIDIA GA107 [GeForce RTX 2050] driver: nvidia v: 575.64
  Device-3: Luxvisions Innotech Integrated Camera driver: uvcvideo type: USB
  Display: wayland server: Xwayland v: 24.1.8 compositor: kwin_wayland
    driver: gpu: i915 resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.0.7
    renderer: Mesa Intel Graphics (ADL GT2)
  API: Vulkan v: 1.4.313 drivers: intel,nvidia,llvmpipe surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio driver: snd_hda_intel
  Device-2: NVIDIA GA107 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.15.3-200.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.5 status: active
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp7s0 state: down mac: <filter>
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network
    driver: rtw89_8852be
  IF: wlp8s0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: N/A
Drives:
  Local Storage: total: 476.94 GiB used: 7.83 GiB (1.6%)
  ID-1: /dev/nvme0n1 vendor: KIOXIA model: SSSTC CL4-4D512-Q62
    size: 476.94 GiB
Partition:
  ID-1: / size: 475.34 GiB used: 7.41 GiB (1.6%) fs: btrfs dev: /dev/dm-0
  ID-2: /boot size: 973.4 MiB used: 402 MiB (41.3%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 27.3 MiB (4.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 475.34 GiB used: 7.41 GiB (1.6%) fs: btrfs
    dev: /dev/dm-0
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 43.5 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15.34 GiB used: 4.56 GiB (29.8%)
  Processes: 930 Uptime: 47m Shell: Bash inxi: 3.3.38

Having the same issue with the same headphones on Kinoite. Updated Kinoite from 42.20250613.0 to 42.20250625.0 and noticed it, so I rolled back. Tried 42.20250626.0 today and still having the same issue.

It’s curious you mention KDE. KDE has been the source of my worst issues right now, and it may be related to this too somehow, because once I restart the bluetooth service, it works fine (disconnecting and connecting the headphones again) through the day until something happens that I need to restart it again, and, it feels like it happens every morning, after I used KDE Connect to control my laptop from bed the previous night and then I close it the morning after, the Stop Button that appears on the top bar as shown here:

image

Not only that, but for example, today, I could not click any icon on the Dash/Dock and also Top Bar. Some windows, like say, Software or Notes, if I clicked anywhere in them, they’d minimize themselves, as if they were unfocused. The x on the tabs of my browser weren’t responsive either, and the only thing that fixed all this was clicking that stop button, which is KDE. Closing/Stopping it fixed those issues, so, maybe it is also meddling with the sound/headphones somehow, the coincidence doesn’t seem that far judging by this in my opinion.

Also, to connect my phone to the laptop using KDE, it’s very common that I have to run these commands at least once or multiple times until it works:

This is why I have them in my Notes, to quickly fix these things, lol, but yeah, the phone will not get detected until I run those two either once or sometimes multiple times, it’s pretty random.

I think it is related to KDE, before Fedora i was using Linux Mint on this laptop, and bluetooth never showed any issues. Also, i tested a fresh install of Fedora 42 Gnome, and bluetooth worked fine, without any problems on weird behavior. Although i only tested my headphones and a generic PS4 controller (fine on Fedora Gnome, but only work after systemctl restart on Fedora KDE).

I tested KDE Connect, and the only issue i have is browse my device wont work, it makes the file manager not responsive, and i cant kill it successfully with anything, the only working solution is to disconnect my phone from kde connect.

Does it happen to you after a reboot too? Every time I reboot, whether it be to install updates or moving the laptop somewhere else, Bluetooth won’t work either, without having used KDE or my phone yet

It happens whenever I reboot, but after I restart the bluetooth service it works fine. I’ve never used KDE connect so I don’t know if that also makes the issue pop up too. Basically after I reboot I can see the bluetooth devices, they’ll all connect, then they’ll disconnect a few seconds later. Then after I restart the service everything works as you’d expect.
I did notice that the first time I had this issue, a welcome window also popped up after boot saying that Plasma had been updated with new features.

1 Like

Yes, it happens everytime after login (after reboot,logoff, or any crash), so i need to manually restart the bluetooth, and sometimes i need to restart again randomly because it wont get the high definition profile.

I don’t know if it’s happening to you too, but quite a few things are broken since the last KDE update, widgets sometimes crash plasma, lock screen wont work anymore, and also suspend that is problematic due to the Nvidia GPU, was fine on Gnome, but it wont work anymore on KDE if i have my external monitor connected.

1 Like