staging.inyokaproject.org

Habe das Gefühl...ewig

Schnell Version,der Reihe nach abarbeiten

pkill -x blueman-manager
pkill -x blueman-applet
sudo pkill -x bluetoothd
sudo rm -r /var/lib/bluetooth/*

Neustart!

Danach

blueman-manager

Das sollte den Grafischen Bluetooth Manager aktivieren. Verbinde die Tastatur und wähle den gelben Stern danach für "Vertrauen". Da das ganze im Terminal läuft zeige die Ausgabe.

kurt@kurt-1000HE:~$ blueman-manager
_________
Load (/usr/lib/python3/dist-packages/blueman/main/PluginManager.py:60)
['Services', 'PulseAudioProfile'] 
_________
__load_plugin (/usr/lib/python3/dist-packages/blueman/main/PluginManager.py:133)
loading <class 'blueman.plugins.manager.Services.Services'> 
_________
__load_plugin (/usr/lib/python3/dist-packages/blueman/main/PluginManager.py:133)
loading <class 'blueman.plugins.manager.PulseAudioProfile.PulseAudioProfile'> 
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
1 
blueman-manager version 2.0.4 starting
Stale PID, overwriting
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
2 
_________
on_bluez_name_owner_changed (/usr/bin/blueman-manager:96)
org.bluez owner changed to  :1.2 
_________
get_interface_version (/usr/lib/python3/dist-packages/blueman/bluez/BlueZInterface.py:13)
Detected BlueZ 5 
_________
SetAdapter (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:271)
 
_________
on_adapter_changed (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerToolbar.py:83)
toolbar adapter /org/bluez/hci0 
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
3 
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
4 
_________
on_pa_ready (/usr/lib/python3/dist-packages/blueman/plugins/manager/PulseAudioProfile.py:29)
connected 
_________
<lambda> (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:353)
1 
_________
on_property_changed (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:155)
adapter propery changed Discovering 1 
_________
on_device_created (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:253)
created /org/bluez/hci0/dev_34_88_5D_22_C6_42 
_________
__init__ (/usr/lib/python3/dist-packages/blueman/main/Device.py:26)
caching initial properties 
_________
add_device (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:317)
adding new device 
_________
do_cache (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:496)
Caching new device 34:88:5D:22:C6:42 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Fake False 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Trusted 0 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Paired 0 
_________
on_property_changed (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:155)
adapter propery changed Discovering 0 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
34-88-5D-22-C6-42 
_________
__setattr__ (/usr/lib/python3/dist-packages/blueman/main/Device.py:118)
Setting property Trusted True 
_________
on_device_property_changed (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:163)
list: device_prop_ch Trusted 1 /org/bluez/hci0/dev_34_88_5D_22_C6_42 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Trusted 1 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
34-88-5D-22-C6-42 
_________
on_device_property_changed (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:163)
list: device_prop_ch Connected 1 /org/bluez/hci0/dev_34_88_5D_22_C6_42 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Connected 1 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
Logitech Keyboard K480 
_________
monitor_power_levels (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:185)
starting monitor 
_________
level_setup_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:325)
animating up 
_________
on_device_property_changed (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:163)
list: device_prop_ch Name Logitech Keyboard K480 /org/bluez/hci0/dev_34_88_5D_22_C6_42 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Name Logitech Keyboard K480 
_________
on_device_property_changed (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:163)
list: device_prop_ch Alias Logitech Keyboard K480 /org/bluez/hci0/dev_34_88_5D_22_C6_42 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Alias Logitech Keyboard K480 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
_________
on_device_property_changed (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:163)
list: device_prop_ch Connected 0 /org/bluez/hci0/dev_34_88_5D_22_C6_42 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Connected 0 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
Logitech Keyboard K480 
_________
level_setup_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:325)
animating down 
_________
update (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:186)
stopping monitor (not connected) 

Die wollen nicht so recht miteinander ☹ Probiere mal

sudo btmgmt le on

kurt@kurt-1000HE:~$ sudo btmgmt le on
[sudo] Passwort für kurt: 
Set Low Energy for hci0 failed with status 0x0c (Not Supported)
kurt@kurt-1000HE:~$ 

Jetzt ist guter Rat teuer 😇 Hat tomtomtom vielleicht noch eine Idee ? Zeige noch

dmesg | grep Blue

und

id

kurt@kurt-1000HE:~$ dmesg | grep Blue
[   27.164696] Bluetooth: Core ver 2.22
[   27.164790] Bluetooth: HCI device and connection manager initialized
[   27.164801] Bluetooth: HCI socket layer initialized
[   27.164808] Bluetooth: L2CAP socket layer initialized
[   27.164827] Bluetooth: SCO socket layer initialized
[   41.709181] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   41.709186] Bluetooth: BNEP filters: protocol multicast
[   41.709199] Bluetooth: BNEP socket layer initialized
[  115.775841] Bluetooth: RFCOMM TTY layer initialized
[  115.775859] Bluetooth: RFCOMM socket layer initialized
[  115.775883] Bluetooth: RFCOMM ver 1.11
kurt@kurt-1000HE:~$ id
uid=1000(kurt) gid=1000(kurt) Gruppen=1000(kurt),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),118(lpadmin),124(sambashare)
kurt@kurt-1000HE:~$ 

Mal was Versuchen,füge dich zur Gruppe lp und Bluetooth hinzu

sudo adduser $USER lp
sudo adduser $USER bluetooth

Neustart.

Hallo Kellerkind,

ich habe beides durchgeführt. Leider ändert sich nichts. Ich muss nach jedem Neustart in die Bluetooth Umgebung Geräte wechseln. Dort ist die Tastatur zwar vermerkt aber nicht mehr aktiviert. Eine Aktivierung durch einschalten des Tastatur funzt nicht, soll heißen ich muss die Tastatur immer durch einrichten neu initialisieren.

Dann bekommt die Tastatur immer einen neuen Key - warum kann ich nicht sagen.Zeige mal wenn alles Funktioniert und verwendet werden kann

lsusb

lsusb -t

vielleicht sieht man da noch was 😇

kurt@kurt-1000HE:~$ lsusb
Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc. Broadcom Bluetooth 2.1
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
kurt@kurt-1000HE:~$ lsusb -t
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 1: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 1: Dev 2, If 2, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 1: Dev 2, If 3, Class=Application Specific Interface, Driver=, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
    |__ Port 8: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 8: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
kurt@kurt-1000HE:~$ 

Hast du einen extra Dongle dran dafür? Ist das eine Combo aus Maus/Tastatur?

Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver

Zeige auch noch

dpkg -l | grep -i libinput

xinput

Formatierter Text

Nein kein Dongle für die Tastatur. Denke ist meine Maus was wir da sehen über USB.

kurt@kurt-1000HE:~$ dpkg -l | grep -i libinput
ii  libinput-bin                          1.8.2-1ubuntu2                              i386         input device management and event handling library - udev quirks
ii  libinput10:i386                       1.8.2-1ubuntu2                              i386         input device management and event handling library - shared library
ii  xserver-xorg-input-libinput           0.25.0-0ubuntu1                             i386         X.Org X server -- libinput input driver
kurt@kurt-1000HE:~$ xinput
Die Anwendung »xinput« ist momentan nicht installiert. Sie können sie durch folgende Eingabe installieren:
sudo apt install xinput
kurt@kurt-1000HE:~$ 

Es gibt Hoffnung https://wiki.archlinux.org/index.php/Bluetooth_keyboard und https://gist.github.com/sergshabal/7f2ec47cfaaf2bb02bc66deec72ff17c

Das ganze lässt sich "Automatisieren" 😉