Enable Bluetooth on login

System:
  Kernel: 6.3.6-273-tkg-bmq arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: intel_pstate=passive split_lock_detect=off intel_pstate=passive
    BOOT_IMAGE=/@/boot/vmlinuz-linux-linux-tkg-bmq-generic_v3
    root=UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d rw rootflags=subvol=@ rd.udev.log_priority=3
    vt.global_cursor_default=0 loglevel=3 sysrq_always_enabled=1 amdgpu.ppfeaturemask=0xffffffff
    nowatchdog nmi_watchdog=0 initrd=@\boot\initramfs-linux-tkg-bmq-generic_v3.img
  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.9 wm: kwin_wayland vt: 1 dm: N/A
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: X470 Taichi serial: <superuser required>
    UEFI: American Megatrends v: P5.10 date: 10/20/2022
CPU:
  Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check
    built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2
    microcode: 0xA20120A
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 4472 high: 4485 min/max: 2200/4650 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 4479 2: 4475 3: 4475 4: 4485 5: 4476 6: 4478
    7: 4466 8: 4477 9: 4475 10: 4450 11: 4474 12: 4454 bogomips: 88889
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Gigabyte
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: DP-2
    bus-ID: 10:00.0 chip-ID: 1002:73df class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 compositor: kwin_wayland
    driver: N/A d-rect: 5120x1728 display-ID: 0
  Monitor-1: DP-1 pos: bottom-r res: 2048x864 size: N/A modes: N/A
  Monitor-2: HDMI-A-1 pos: top-center res: 1536x864 size: N/A modes: N/A
  Monitor-3: HDMI-A-2 pos: primary,top-left res: 1536x864 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 23.1.1 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.7 DRM 3.52
    6.3.6-273-tkg-bmq) direct-render: Yes
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 10:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 12:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Sony INZONE H9 / H7 driver: cdc_acm,hid-generic,snd-usb-audio,usbhid type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 054c:0e53 class-ID: 0a00
  API: ALSA v: k6.3.6-273-tkg-bmq status: kernel-api with: aoss type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 0.3.71 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 08:00.0 chip-ID: 8086:24fb class-ID: 0280
  IF: wlp8s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 0a:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Edimax Bluetooth Adapter driver: btusb v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 5-1:2 chip-ID: 7392:c611 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: no address: <filter>
Drives:
  Local Storage: total: 2.96 TiB used: 4.11 TiB (139.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 3B4QFXO7 temp: 41.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXE7 temp: 34.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DX002-2DV164 size: 1.82 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: CC41 scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 836.53 GiB (89.8%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 27.8 MiB (9.3%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:4
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 836.53 GiB (89.8%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 836.53 GiB (89.8%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 836.53 GiB (89.8%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 70.0 C mobo: 37.0 C gpu: amdgpu temp: 53.0 C mem: 56.0 C
  Fan Speeds (RPM): fan-1: 0 fan-2: 2238 fan-3: 0 fan-4: 0 fan-5: 0 gpu: amdgpu fan: 954
  Power: 12v: N/A 5v: N/A 3.3v: 3.14 vbat: 3.28 gpu: amdgpu watts: 33.00
Info:
  Processes: 468 Uptime: 0m wakeups: 0 Memory: available: 31.26 GiB used: 9.7 GiB (31.0%)
  Init: systemd v: 253 default: graphical tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7
  Packages: 2585 pm: pacman pkgs: 2557 libs: 585 tools: octopi,paru pm: appimage pkgs: 0
  pm: flatpak pkgs: 28 Client: shell wrapper v: 5.1.16-release inxi: 3.3.27
Garuda (2.6.16-1):
  System install date:     2023-05-07
  Last full system update: 2023-06-05
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:


Bluetooth is always disabled on login, meaning i have to go into the Bluetooth kde applet and enable it whenever i want to connect something.

Under the kde settings i found a setting for controlling Bluetooth state on login but that seems to have no affect and is always disabled on login

looking a bit online and on other post saw there is a option for this in /etc/bluetooth/main.conf but its already enabled for me

# timeout). The policy plugin should contain a sane set of values by
# default, but this list can be overridden here. By setting the list to
# empty the reconnection feature gets disabled.
#ReconnectUUIDs=00001112-0000-1000-8000-00805f9b34fb,0000111f-0000-1000-8000-00805f9b34fb,0000110a-0000-10
00-8000-00805f9b34fb,0000110b-0000-1000-8000-00805f9b34fb

# ReconnectAttempts define the number of attempts to reconnect after a link
# lost. Setting the value to 0 disables reconnecting feature.
#ReconnectAttempts=7

# ReconnectIntervals define the set of intervals in seconds to use in between
# attempts.
# If the number of attempts defined in ReconnectAttempts is bigger than the
# set of intervals the last interval is repeated until the last attempt.
#ReconnectIntervals=1,2,4,8,16,32,64

# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'true'.
AutoEnable=true

# Audio devices that were disconnected due to suspend will be reconnected on
# resume. ResumeDelay determines the delay between when the controller
# resumes from suspend and a connection attempt is made. A longer delay is
# better for better co-existence with Wi-Fi.
# The value is in seconds.
# Default: 2
#ResumeDelay = 2

[AdvMon]
# Default RSSI Sampling Period. This is used when a client registers an
# advertisement monitor and leaves the RSSISamplingPeriod unset.
# Possible values:
# 0x00       Report all advertisements
# N = 0xXX   Report advertisements every N x 100 msec (range: 0x01 to 0xFE)
# 0xFF       Report only one advertisement per device during monitoring period
# Default: 0xFF
#RSSISamplingPeriod=0xFF

Quick google search revealed this: linux - Turn on bluetooth on login screen - Unix & Linux Stack Exchange

1 Like

yeah, I saw similar answers online. Apparently in older versions of bluez Bluetooth was disabled on startup by default but this is no longer the case in newer versions I even have the AutoEnable option in my config.

what about systemctl status bluetooth is it even enabled?

1 Like
 bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Mon 2023-06-05 17:48:31 EDT; 35s ago
       Docs: man:bluetoothd(8)
   Main PID: 748 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38368)
     Memory: 4.6M
        CPU: 38ms
     CGroup: /system.slice/bluetooth.service
             ā””ā”€748 /usr/lib/bluetooth/bluetoothd

Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/faststream
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/opus_05
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/opus_05
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jun 05 17:48:37 Garuda-Linux bluetoothd[748]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jun 05 17:48:38 Garuda-Linux bluetoothd[748]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down

Output of rfkill list, please?

('rfkill' is a utility for turning radio frequency (rf) devices. 'list' will show what devices it can see, and if they are set on or off for "soft" and "hard".)

1 Like

It will show soft block since it's disabled in kde settings

That's exactly what I'm trying to resolve.

I don't want kde to put it in a disabled state i.e soft blocked

EDIT: huh nope I was wrong it not even blocked according rfkill i could of sworn i saw it soft blocked before. This is after a reboot were Bluetooth is not working and is disabled in kde settings

0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Iā€™d work on that disabled preset.

2 Likes

How do I do that? Doesn't that just mean the systemd service is disabled by default on Install but is enabled now?

On boot it shows as enabled

Have you searched in the KDE Bug Tracking System?
This one seems interesting, but I didn't have time to search further:
https://bugs.kde.org/show_bug.cgi?id=469119

3 Likes

That does look like my issue. Didn't think to look on the kde bug tracker specificly as it works as expected for other people so it seemed like it was something misconfigured on my system

Yup apparently it's the exact same bug with the same fix just change

[Adapters]
Your Bluetooth adapter mac_powered=true

in ~/.config/bluedevilglobalrc

Apparently it gets set to false sometimes for some reason but doesn't seem to happen to everyone

EDIT: keeps getting set to false every time I open the bluetooth config module. If i don't touch that it stays set true and is enabled and powered on login ( guess there two different things)

another 'fix' is after setting the powered option to true make the file read-only so that it doesn't get set to false again

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.