You are not logged in.
Hi,
I've got a pair of AKG Y50 headphones which work intermittently on my machine, just now their not! Here's the log I can see from from systemd journal:
Jul 03 14:57:53 trantor bluetoothd[678]: /org/bluez/hci0/dev_34_DF_2A_51_0C_B9/sep1/fd7: fd(46) ready
Jul 03 14:57:53 trantor rtkit-daemon[1288]: Supervising 13 threads of 9 processes of 2 users.
Jul 03 14:57:53 trantor rtkit-daemon[1288]: Successfully made thread 80074 of process 1185 owned by '120' RT at priority 5.
Jul 03 14:57:53 trantor rtkit-daemon[1288]: Supervising 14 threads of 9 processes of 2 users.
Jul 03 14:57:54 trantor kernel: input: AKG Y50BT (AVRCP) as /devices/virtual/input/input40
Jul 03 14:57:54 trantor systemd-logind[682]: Watching system buttons on /dev/input/event25 (AKG Y50BT (AVRCP))
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[886]: (II) config/udev: Adding input device AKG Y50BT (AVRCP) (/dev/input/event25)
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[886]: (**) AKG Y50BT (AVRCP): Applying InputClass "libinput keyboard catchall"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[886]: (**) AKG Y50BT (AVRCP): Applying InputClass "system-keyboard"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[886]: (II) Using input driver 'libinput' for 'AKG Y50BT (AVRCP)'
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) config/udev: Adding input device AKG Y50BT (AVRCP) (/dev/input/event25)
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) AKG Y50BT (AVRCP): Applying InputClass "libinput keyboard catchall"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) AKG Y50BT (AVRCP): Applying InputClass "system-keyboard"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) Using input driver 'libinput' for 'AKG Y50BT (AVRCP)'
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) systemd-logind: got fd for /dev/input/event25 13:89 fd 66 paused 0
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) AKG Y50BT (AVRCP): always reports core events
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) Option "Device" "/dev/input/event25"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) Option "_source" "server/udev"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[886]: (II) systemd-logind: got fd for /dev/input/event25 13:89 fd 25 paused 1
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[886]: (II) systemd-logind: releasing fd for 13:89
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) event25 - AKG Y50BT (AVRCP): is tagged by udev as: Keyboard
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) event25 - AKG Y50BT (AVRCP): device is a keyboard
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) event25 - AKG Y50BT (AVRCP): device removed
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input40/event25"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) XINPUT: Adding extended input device "AKG Y50BT (AVRCP)" (type: KEYBOARD, id 19)
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) Option "xkb_layout" "gb"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (**) Option "xkb_variant" "extd"
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) event25 - AKG Y50BT (AVRCP): is tagged by udev as: Keyboard
Jul 03 14:57:54 trantor /usr/lib/gdm-x-session[1417]: (II) event25 - AKG Y50BT (AVRCP): device is a keyboard
Seems to me like the headphones are being registered as a keyboard, which would explain why they don't appear in the
Gnome settings panel under output devices!
Can anybody help?
Last edited by r-giskard-reventlov (2020-07-04 10:24:03)
Offline
Please wrap outputs in [ code ] [ /code ] tags without the spaces.
Every device that has any kind of button gets registered as a keyboard in xorg, this makes no statement at how available it should be for other purposes. This needs more logs either from kernel/bluetoothd and/or pulseaudio. Have you read https://wiki.archlinux.org/index.php/Bluetooth_headset and particularly: https://wiki.archlinux.org/index.php/Bl … e_with_GDM ?
Online
I read it. But I have no solution. My bluetooth headset keeps disconnecting. Should I write a udev rule and tell this MAC address device is a headset?
Jul 14 11:24:39 lalaland.net systemd[1]: Reached target Bluetooth Support.
░░ Subject: A start job for unit bluetooth.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit bluetooth.target has finished successfully.
░░
░░ The job identifier is 6558.
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/ldac
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSink/aptx_hd
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/aptx_hd
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSink/aptx
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/aptx
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/aac
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSink/sbc
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/sbc
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSink/sbc_xq
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/sbc_xq
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/faststream
Jul 14 11:24:40 lalaland.net bluetoothd[1156]: Endpoint registered: sender=:1.104 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jul 14 11:24:44 lalaland.net bluetoothd[1156]: /org/bluez/hci0/dev_1C_52_16_B1_66_86/sep1/fd9: fd(38) ready
Jul 14 11:24:44 lalaland.net kernel: input: Redmi AirDots_R (AVRCP) as /devices/virtual/input/input32
Jul 14 11:24:44 lalaland.net systemd-logind[1197]: Watching system buttons on /dev/input/event20 (Redmi AirDots_R (AVRCP))
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) config/udev: Adding input device Redmi AirDots_R (AVRCP) (/dev/input/event20)
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Redmi AirDots_R (AVRCP): Applying InputClass "evdev keyboard catchall"
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Redmi AirDots_R (AVRCP): Applying InputClass "libinput keyboard catchall"
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Redmi AirDots_R (AVRCP): Applying InputClass "system-keyboard"
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) Using input driver 'libinput' for 'Redmi AirDots_R (AVRCP)'
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) systemd-logind: got fd for /dev/input/event20 13:84 fd 106 paused 0
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Redmi AirDots_R (AVRCP): always reports core events
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Option "Device" "/dev/input/event20"
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Option "_source" "server/udev"
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) event20 - Redmi AirDots_R (AVRCP): is tagged by udev as: Keyboard
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) event20 - Redmi AirDots_R (AVRCP): device is a keyboard
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) event20 - Redmi AirDots_R (AVRCP): device removed
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input32/event20"
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) XINPUT: Adding extended input device "Redmi AirDots_R (AVRCP)" (type: KEYBOARD, id 19)
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (**) Option "xkb_layout" "us"
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) event20 - Redmi AirDots_R (AVRCP): is tagged by udev as: Keyboard
Jul 14 11:24:44 lalaland.net /usr/libexec/gdm-x-session[2639]: (II) event20 - Redmi AirDots_R (AVRCP): device is a keyboard
Jul 14 11:24:44 lalaland.net systemd[1]: systemd-rfkill.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-rfkill.service has successfully entered the 'dead' state.
Offline
don't appear in the Gnome settings panel under output devices
My bluetooth headset keeps disconnecting
And neither is reflected by the limited journal you posted ("sudo journacltl -b", no filter, no "-x" either)
https://wiki.archlinux.org/title/Blueto … ew_moments
Is the BT an USB dongle?
https://wiki.archlinux.org/title/Power_ … utosuspend
Offline