[РЕШЕНО] Bluetooth без gnome or KDE, а именно sway bluetooth

lnx · # 02.01.2026 11:20

Коллеги, опять был НГ и опять были сюрпризы. Вот мигрировал я с гнома на sway летом и это был первый НГ, когда традиционно требует БТ для музыки на колонках. Все нужное стоит, служба запущена, устройство есть, а blueman ничего не показывает и не дает -

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 04f2:b756 Chicony Electronics Co., Ltd Integrated Camera
Bus 003 Device 003: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub


bluetoothctl
[NEW] Media /org/bluez/hci0 
	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 64:D6:9A:A0:3A:65 Pairable: yes
hci0 new_settings: bondable ssp br/edr le secure-conn wide-band-speech cis-central cis-peripheral ll-privacy 

hcitool scan
Device is not available: No such device

bluetoothctl power on
Failed to set power on: org.bluez.Error.Failed
# bluetoothctl power off
Changing power off succeeded
# bluetoothctl power on
Failed to set power on: org.bluez.Error.Failed


systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Thu 2026-01-01 23:50:21 MSK; 11h ago
 Invocation: 0e79b4939ca64aa5804ad8863f85dad5
       Docs: man:bluetoothd(8)
   Main PID: 22798 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18803)
     Memory: 1008K (peak: 2.3M)
        CPU: 39ms
     CGroup: /system.slice/bluetooth.service
             └─22798 /usr/lib/bluetooth/bluetoothd

ЧЯДНТ?

lnx · # 02.01.2026 11:34

Безусловно, полезно читать - https://wiki.archlinux.org/title/Blueto ... %B8%D0%B9)

journalctl | grep hci
янв 01 23:41:54 WAU kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
янв 01 23:41:54 WAU kernel: xhci_hcd 0000:00:14.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000100200009810
янв 01 23:41:54 WAU kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
янв 01 23:41:54 WAU kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
янв 01 23:41:54 WAU kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
янв 01 23:41:54 WAU kernel: usb usb3: Manufacturer: Linux 6.18.2-arch2-1 xhci-hcd
янв 01 23:41:54 WAU kernel: usb usb4: Manufacturer: Linux 6.18.2-arch2-1 xhci-hcd
янв 01 23:41:54 WAU kernel: usb 3-8: new high-speed USB device number 2 using xhci_hcd
янв 01 23:41:54 WAU kernel: usb 3-10: new full-speed USB device number 3 using xhci_hcd
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Device revision is 0
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Secure boot is enabled
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: OTP lock is enabled
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: API lock is enabled
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Debug lock is disabled
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: DSM reset method type: 0x00
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Boot Address: 0x100800
янв 01 23:41:55 WAU kernel: Bluetooth: hci0: Firmware Version: 133-20.25
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Waiting for firmware download to complete
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Firmware loaded in 1557302 usecs
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Waiting for device to boot
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Device booted in 15163 usecs
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Firmware timestamp 2025.20 buildtype 1 build 82053
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Firmware SHA1: 0x937bca4a
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Fseq status: Success (0x00)
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Fseq executed: 00.00.02.41
янв 01 23:41:57 WAU kernel: Bluetooth: hci0: Fseq BT Top: 00.00.02.41

lnx · # 06.01.2026 15:58

все-ж таки, есть какие-либо идеи на тему "как его заставить работать"?

bluetoothctl
[NEW] Media /org/bluez/hci0 
	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000FDF0-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 64:D6:9A:A0:3A:65 Pairable: yes
hci0 new_settings: bondable ssp br/edr le secure-conn wide-band-speech cis-central cis-peripheral ll-privacy 
AdvertisementMonitor path registered
[bluetoothctl]> power on
Failed to set power on: org.bluez.Error.Failed


list
Controller 64:D6:9A:A0:3A:65 WAU_n [default]

show 64:D6:9A:A0:3A:65
Controller 64:D6:9A:A0:3A:65 (public)
	Manufacturer: 0x0002 (2)
	Version: 0x0d (13)
	Name: WAU
	Alias: WAU_n
	Class: 0x00000000 (0)
	Powered: no
	PowerState: off-blocked
	Discoverable: no
	DiscoverableTimeout: 0x00000000 (0)
	Pairable: yes
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
	UUID: Volume Offset Control     (00001845-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Volume Control            (00001844-0000-1000-8000-00805f9b34fb)
	UUID: Microphone Control        (0000184d-0000-1000-8000-00805f9b34fb)
	UUID: Audio Input Control       (00001843-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: Broadcast Audio Scan      (0000184f-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0555
	Discovering: no
	Roles: central
	Roles: peripheral
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x0c (12)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
	SupportedSecondaryChannels: 1M
	SupportedSecondaryChannels: 2M
	SupportedSecondaryChannels: Coded
	SupportedCapabilities.MinTxPower: 0xffffffde (-34)
	SupportedCapabilities.MaxTxPower: 0x0007 (7)
	SupportedCapabilities.MaxAdvLen: 0xfb (251)
	SupportedCapabilities.MaxScnRspLen: 0xfb (251)
	SupportedFeatures: CanSetTxPower
	SupportedFeatures: HardwareOffload
Advertisement Monitor Features:
	SupportedMonitorTypes: or_patterns
	SupportedFeatures: controller-patterns

есть ощущение, что sway апплет сети не умеет работать с блютузом?

lnx · # 06.01.2026 16:08

ну да. Так и оказалось. Требует апплет. Решение - вписать в зону автостарта sway -

blueman-applet

Но это странно. Так не должно быть. Ведь ключевой компонент - blueman, он есть, запускается. Но до запуска апплета адаптер, который система видит и пр., сам blueman не видит.