Willkommen Gast. Bitte einloggen oder registrieren. Haben Sie Ihre Aktivierungs E-Mail übersehen?
13.05.2021, 15:34:57

.
Einloggen mit Benutzername, Passwort und Sitzungslänge

Mitglieder
  • Mitglieder insgesamt: 25587
  • Letzte: Waber
Statistiken
  • Beiträge insgesamt: 735004
  • Themen insgesamt: 59211
  • Heute online: 687
  • Am meisten online: 2287
  • (22.01.2020, 19:20:24)
Benutzer Online

Autor Thema:  LM20.1 Cin. Bluetooth-Maus Aussetzer nach Benutzeranmeldung  (Gelesen 273 mal)

0 Mitglieder und 1 Gast betrachten dieses Thema.

Hallo,
im anderen Thema hatte ich kürzlich meine Logitech Bluetooth Maus i]MX Anywhere 2S[/i] installiert:
https://www.linuxmintusers.de/index.php?topic=65769.0

Symptome:
Die Bluetooth Maus besitzt keinen BT-Dongle sondern setzt auf das interne BT-Modul des Notebook. Leider besteht Hier auf beiden LM20.1Cin. Installationen das selbe Problem das die BT-Maus nach Neustart oder Ruhebetrieb nach der Benutzeranmeldung zuerst für ca. fünf (5) Sekunden verfügbar ist um dann ihren Dienst für ca. fünf (5) Sekunden zu verweigern. Conky zeigt während dessen 15% Prozessorlast, anschließend ist die BT-Maus dauerhaft verfügbar.

Mein System:
kuehhe1@LM20-1-Test:~$ inxi -Fz
System:    Kernel: 5.4.0-67-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa
Machine:   Type: Laptop System: HP product: HP ProBook 470 G5 v: N/A serial: <filter>
           Mobo: HP model: 837F v: KBC Version 02.3E.00 serial: <filter> UEFI: HP v: Q85 Ver. 01.14.01 date: 10/19/2020
Battery:   ID-1: BAT0 charge: 34.5 Wh condition: 36.9/48.0 Wh (77%)
CPU:       Info: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP L2 cache: 6144 KiB
           Speed: 806 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 700 2: 700 3: 700 4: 700 5: 700 6: 700 7: 700 8: 700
Graphics:  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
           Device-2: NVIDIA GM108M [GeForce 930MX] driver: nvidia v: 460.39
           Device-3: Lite-On HP HD Camera type: USB driver: uvcvideo
           Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1600x900~60Hz
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.2.6
Audio:     Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
           Sound Server: ALSA v: k5.4.0-67-generic
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           IF: enp2s0 state: down mac: <filter>
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi
           IF: wlp3s0 state: up mac: <filter>
Drives:    Local Storage: total: 1.17 TiB used: 249.36 GiB (20.8%)
           ID-1: /dev/nvme0n1 vendor: SK Hynix model: PC401 HFS256GD9TNG-62A0A size: 238.47 GiB
           ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
           ID-3: /dev/sdb type: USB vendor: Intenso model: Slim Line size: 29.30 GiB
Partition: ID-1: / size: 39.38 GiB used: 16.73 GiB (42.5%) fs: ext4 dev: /dev/nvme0n1p9
Swap:      ID-1: swap-1 type: partition size: 10.00 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p7
Sensors:   System Temperatures: cpu: 35.0 C mobo: 34.0 C
           Fan Speeds (RPM): N/A
Info:      Processes: 326 Uptime: 4h 19m Memory: 7.21 GiB used: 3.24 GiB (45.0%) Shell: Bash inxi: 3.1.06
kuehhe1@LM20-1-Test:~$ lsusb
Installierte Bluetooth Pakete:kuehhe1@LM20-1-Test:~$ dpkg -l *blue* | egrep '^ii '
ii  blueman                         2.1.2-1ubuntu0.2               amd64        Graphical bluetooth manager
ii  bluetooth                       5.53-0ubuntu3                  all          Bluetooth support
ii  bluez                           5.53-0ubuntu3                  amd64        Bluetooth tools and daemons
ii  bluez-obexd                     5.53-0ubuntu3                  amd64        bluez obex daemon
ii  bluez-tools                     2.0~20170911.0.7cb788c-2build1 amd64        Set of tools to manage Bluetooth devices for linux
ii  gir1.2-gnomebluetooth-1.0:amd64 3.34.3-0ubuntu1                amd64        Introspection data for GnomeBluetooth
ii  gnome-bluetooth                 3.34.3-0ubuntu1                amd64        GNOME Bluetooth tools
ii  libbluetooth3:amd64             5.53-0ubuntu3                  amd64        Library to use the BlueZ Linux Bluetooth stack
ii  libgnome-bluetooth13:amd64      3.34.3-0ubuntu1                amd64        GNOME Bluetooth tools - support library
ii  pulseaudio-module-bluetooth     1:13.99.1-1ubuntu3.10          amd64        Bluetooth module for PulseAudio sound server
kuehhe1@LM20-1-Test:~$

Obwohl die BT-Maus LED dauerhaft leuchtet wird anscheinend die Bluetooth Verbindung kurzzeitig abgebaut was auch am Farbwechsel des Bluetooth-Leisten-Applet und im Fenster: Bluetooth-Geräte erkennbar ist. Die drei (3) Farbbalken verschwinden dann und werden erst nach den fünf (5) Gedenksekunden wieder sichtbar, siehe Screenshot #1

Über das Blueman-Applet, habe ich die Standards versuchsweise verändert:
in Geräte die: MX Anywhere 2S als Vertraulich markiert, verbessert nichts,
in Erweiterungen > Power-Manager de- aktiviert, verbessert nichts.
in Erweiterungen > Power-Manager > Einstellungen : das automatische Einschalten de- aktiviert, verbessert nichts.
in Erweiterungen > Kill-Switch de- aktiviert, verbessert nichts.
siehe dazu Screenshot #2+3

Im Log: /var/log/sys.log finden sich zu BT diese Meldungen an denen die Bluetooth Unterbrechung erkennbar ist:Mar 18 19:41:50 LM20-1-Test systemd[1531]: Reached target Bluetooth.
Mar 18 19:41:50 LM20-1-Test systemd[1631]: Reached target Bluetooth.
Mar 18 19:41:51 LM20-1-Test bluetoothd[874]: bt_uhid_send: Invalid argument (22)
Mar 18 19:41:51 LM20-1-Test kernel: [   28.074602] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0002/input/input32
Mar 18 19:41:51 LM20-1-Test kernel: [   28.074744] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0002/input/input33
Mar 18 19:41:51 LM20-1-Test kernel: [   28.074931] hid-generic 0005:046D:B01A.0002: input,hidraw1: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 7c:76:35:99:a1:91
Mar 18 19:41:51 LM20-1-Test bluetoothd[874]: message repeated 8 times: [ bt_uhid_send: Invalid argument (22)]
Mar 18 19:41:52 LM20-1-Test /hp-systray: hp-systray(qt5)[2618]: error: Unable to find hp-upgrade --notify on PATH.
Mar 18 19:41:53 LM20-1-Test cinnamon-session[1646]: WARNING: t+7,09062s: Detected that screensaver has appeared on the bus
Mar 18 19:41:56 LM20-1-Test systemd[1]: Stopping User Manager for UID 120...
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped target Bluetooth.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped target Main User Target.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopping Accessibility services bus...
Mar 18 19:41:56 LM20-1-Test gvfsd[1579]: A connection to the bus can't be made
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopping D-Bus User Message Bus...
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopping Virtual filesystem service...
Mar 18 19:41:56 LM20-1-Test systemd[1531]: dbus.service: Killing process 1559 (gdbus) with signal SIGKILL.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: at-spi-dbus-bus.service: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped Accessibility services bus.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: dbus.service: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1]: run-user-120-gvfs.mount: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1631]: run-user-120-gvfs.mount: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped D-Bus User Message Bus.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: run-user-120-gvfs.mount: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: gvfs-daemon.service: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped Virtual filesystem service.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped target Basic System.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped target Paths.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped target Sockets.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped target Timers.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: dbus.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed D-Bus User Message Bus Socket.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: dirmngr.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed GnuPG network certificate management daemon.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: gpg-agent-browser.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 18 19:41:56 LM20-1-Test systemd[1531]: gpg-agent-extra.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 18 19:41:56 LM20-1-Test systemd[1531]: gpg-agent-ssh.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 18 19:41:56 LM20-1-Test systemd[1531]: gpg-agent.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: pk-debconf-helper.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed debconf communication socket.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: pulseaudio.socket: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Closed Sound System.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Reached target Shutdown.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: systemd-exit.service: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Finished Exit the Session.
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Reached target Exit the Session.
Mar 18 19:41:56 LM20-1-Test systemd[1]: user@120.service: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1]: Stopped User Manager for UID 120.
Mar 18 19:41:56 LM20-1-Test systemd[1]: Stopping User Runtime Directory /run/user/120...
Mar 18 19:41:56 LM20-1-Test systemd[1631]: run-user-120.mount: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1]: run-user-120.mount: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1]: user-runtime-dir@120.service: Succeeded.
Mar 18 19:41:56 LM20-1-Test systemd[1]: Stopped User Runtime Directory /run/user/120.
Mar 18 19:41:56 LM20-1-Test systemd[1]: Removed slice User Slice of UID 120.
Mar 18 19:42:03 LM20-1-Test systemd[1]: systemd-fsckd.service: Succeeded.
Mar 18 19:42:04 LM20-1-Test systemd-timesyncd[814]: Initial synchronization to time server 91.189.89.198:123 (ntp.ubuntu.com).
Mar 18 19:42:04 LM20-1-Test systemd[1]: systemd-hostnamed.service: Succeeded.
Mar 18 19:42:20 LM20-1-Test systemd[1]: blueman-mechanism.service: Succeeded.
Mar 18 19:42:21 LM20-1-Test acpid: input device has been disconnected, fd 22
Mar 18 19:42:30 LM20-1-Test bluetoothd[874]: bt_uhid_send: Invalid argument (22)
Mar 18 19:42:30 LM20-1-Test kernel: [   65.930990] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0003/input/input35
Mar 18 19:42:30 LM20-1-Test kernel: [   65.931087] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0003/input/input36
Mar 18 19:42:30 LM20-1-Test kernel: [   65.931193] hid-generic 0005:046D:B01A.0003: input,hidraw1: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 7c:76:35:99:a1:91
Mar 18 19:42:30 LM20-1-Test bluetoothd[874]: bt_uhid_send: Invalid argument (22)
Mar 18 19:45:47 LM20-1-Test wpa_supplicant[910]: wlp3s0: WPA: Group rekeying completed with 38:10:d5:cc:66:83 [GTK=CCMP]

Was bedeutet im sys.log diese Meldungen:Mar 18 19:41:51 LM20-1-Test bluetoothd[874]: bt_uhid_send: Invalid argument (22)
Mar 18 19:41:56 LM20-1-Test systemd[1531]: Stopped target Bluetooth.
denn das ist der Zeitraum in dem die BT-Maus ihren Dienst verweigert.

Lässt sich das Problem auf LM20.1Cin. verbessern oder abstellen?
Vergleichsweise bestehen mit Win10 keine BT-Maus Unterbrechungen.
« Letzte Änderung: 22.03.2021, 09:51:38 von kuehhe1 »

Re: LM20.1 Cin. Bluetooth-Maus Aussetzer nach Benutzeranmeldung
« Antwort #1 am: 22.03.2021, 09:49:30 »
Moin,
habe mich weiter mit dem BT-Maus Aussetzer beschäftigt, nach bluetooth* gesucht und eine bluetooth.service in:
/etc/systemd/system/bluetooth.target.wants/bluetooth.servicegefunden.

die bluetooth.service :[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
ProtectHome=true
ProtectSystem=full

[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service

Darin wird auf: /etc/bluetooth/main.confhingewiesen:[General]

# Default adaper name
# Defaults to 'BlueZ X.YZ'
#Name = BlueZ

# Default device class. Only the major and minor device class bits are
# considered. Defaults to '0x000000'.
#Class = 0x000100

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
#DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
#PairableTimeout = 0

# Automatic connection for bonded devices driven by platform/user events.
# If a platform plugin uses this mechanism, automatic connections will be
# enabled during the interval defined below. Initially, this feature
# intends to be used to establish connections to ATT channels. Default is 60.
#AutoConnectTimeout = 60

# Use vendor id source (assigner), vendor, product and version information for
# DID profile support. The values are separated by ":" and assigner, VID, PID
# and version.
# Possible vendor id source values: bluetooth, usb (defaults to usb)
#DeviceID = bluetooth:1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to 'true'.
#ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
#NameResolving = true

# Enable runtime persistency of debug link keys. Default is false which
# makes debug link keys valid only for the duration of the connection
# that they were created for.
#DebugKeys = false

# Restricts all controllers to the specified transport. Default value
# is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW).
# Possible values: "dual", "bredr", "le"
#ControllerMode = dual

# Enables Multi Profile Specification support. This allows to specify if
# system supports only Multiple Profiles Single Device (MPSD) configuration
# or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple
# Devices (MPMD) configurations.
# Possible values: "off", "single", "multiple"
#MultiProfile = off

# Permanently enables the Fast Connectable setting for adapters that
# support it. When enabled other devices can connect faster to us,
# however the tradeoff is increased power consumptions. This feature
# will fully work only on kernel version 4.1 and newer. Defaults to
# 'false'.
#FastConnectable = false

[Policy]

# The ReconnectUUIDs defines the set of remote services that should try
# to be reconnected to in case of a link loss (link supervision
# 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-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 'false'.
AutoEnable=true

Mein Versuch den darin ausgeremmten: #ReconnectIntervals=1, 2, 4, 8, 16, 32, 64 testweise zu aktivieren zeigte leider nach Neustart keine Verbesserung.

Ab dem Punkt weiss ich nicht weiter. ::)
« Letzte Änderung: 22.03.2021, 16:47:10 von kuehhe1 »

Re: LM20.1 Cin. Bluetooth-Maus Aussetzer nach Benutzeranmeldung
« Antwort #2 am: 22.03.2021, 16:06:57 »
Hi :)
Zitat
#FastConnectable = false

das sticht mir ins auge...

Re: LM20.1 Cin. Bluetooth-Maus Aussetzer nach Benutzeranmeldung
« Antwort #3 am: 22.03.2021, 16:48:36 »
Hi @ehtron.
ist es sinnvoll ihn auf true zu stellen?

FastConnectable = true

Re: LM20.1 Cin. Bluetooth-Maus Aussetzer nach Benutzeranmeldung
« Antwort #4 am: 22.03.2021, 16:50:23 »
Hi :)
wo ist das problem das mal auszuprobieren wenn man nicht mehr weiter weiss... oder bilde einen arbeitskreis ;)

Re: LM20.1 Cin. Bluetooth-Maus Aussetzer nach Benutzeranmeldung
« Antwort #5 am: 22.03.2021, 17:03:12 »
Kein Problem, war nur eine Frage vorab. Der Arbeitskreis "steht" ;)

FastConnectable = trueallein zeigt auch nach Neustart keine Verbesserung,
auch ein zusätzliches:ReconnectIntervals=1, 2, 4, 8, 16, 32, 64bewirkt nichts, die BT-Maus setzt fünf Sekunden aus.

Edit:
umstellen von:AutoEnable=trueauf
AutoEnable=falsebewirkt das die BT-Maus Nicht zur Benutzeranmeldung zur Verfügung steht sondern erst nach Öffnen des Schreibtisches für 5 Sek. bereit ist um nach ca. fünf (5) Sek. auszusetzen und erst nach weiteren fünf (5) Sek. dauerhaft zur Verfügung steht. :(

Edit: Grammatik
« Letzte Änderung: 28.03.2021, 09:50:49 von kuehhe1 »