This forum has been archived. All content is frozen. Please use KDE Discuss instead.

System temporary freeze after connecting a bluetooth device

Tags: bluetooth, shortcuts bluetooth, shortcuts bluetooth, shortcuts
(comma "," separated)
User avatar
simgunz
Registered Member
Posts
56
Karma
0
OS
I have noticed that whenever I connect a bluetooth device (part of) KDE becomes unresponsive. This happen in two different notebooks running Manjaro linux.

Scenario 1:
1. Put notebook to sleep with a bluetooth mouse connected
2. Resume from sleep

Observed result:
I can write a few characters in the password field of the login screen, then the system becomes unresponsive for a few seconds ignoring what is typed, the starts working normally.

Scenario 2:
1. Connect a bluetooth mouse or bluetooth headphone

Observed result:
Global KDE shortcuts (like F12 to trigger yakuake) do not work for a few seconds after 1-2 seconds after connecting the bluetooth device

Code: Select all
System:
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP EliteBook 840 G4 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 828C v: KBC Version 45.3C serial: <superuser required>
    UEFI: HP v: P78 Ver. 01.08 date: 10/17/2017
CPU:
  Info: dual core Intel Core i5-7200U [MT MCP] arch: Amber/Kaby Lake
    note: check speed (MHz): avg: 706 min/max: 400/3100
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: HDMI-A-1,eDP-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:5916 class-ID: 0300
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-7:3 chip-ID: 8087:0a2b class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 105 state: up address: see --recommends


journalctl -f from just after switching the bluetooth mouse on to trigger a connection to when the system becomes responsive again
Code: Select all
feb 28 08:55:15 myhost kernel: input: ProClick Mouse as /devices/virtual/misc/uhid/0005:1532:0076.0132/input/input1381
feb 28 08:55:15 myhost kernel: input: ProClick Consumer Control as /devices/virtual/misc/uhid/0005:1532:0076.0132/input/input1382
feb 28 08:55:15 myhost kernel: input: ProClick System Control as /devices/virtual/misc/uhid/0005:1532:0076.0132/input/input1383
feb 28 08:55:15 myhost kernel: input: ProClick as /devices/virtual/misc/uhid/0005:1532:0076.0132/input/input1384
feb 28 08:55:15 myhost kernel: input: ProClick Keyboard as /devices/virtual/misc/uhid/0005:1532:0076.0132/input/input1385
feb 28 08:55:15 myhost kernel: hid-generic 0005:1532:0076.0132: input,hidraw0: BLUETOOTH HID v0.01 Mouse [ProClick] on 74:e5:f9:84:f5:98
feb 28 08:55:15 myhost systemd-logind[379]: Watching system buttons on /dev/input/event25 (ProClick Keyboard)
feb 28 08:55:15 myhost systemd-logind[379]: Watching system buttons on /dev/input/event10 (ProClick Consumer Control)
feb 28 08:55:15 myhost systemd-logind[379]: Watching system buttons on /dev/input/event23 (ProClick System Control)
feb 28 08:55:16 myhost kcminit[1677478]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_mouse.so"


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], kesang, Yahoo [Bot]