Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

Bug #1834085 reported by whochismo
108
This bug affects 24 people
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed.

However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes.

I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine.

First of all:

Using the command "bluetoothctl" I get the following every time I experience a disconnection:

[CHG] Device F4:1B:A1:33:F9:8D Connected: no
[CHG] Device F4:1B:A1:33:F9:8D Connected: yes

Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections)

[ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
[ 1609.070797] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
[ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
[ 1676.917377] NET: Registered protocol family 38
[ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
[ 1872.815559] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
[ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
[ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
[ 3101.683100] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
[ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
[ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
[ 3110.683929] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
[ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

And this is what journalctl -b shows at the moment of the disconnection/reconnection:

de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed
de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput"
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80
de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device.
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file.
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16)
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "libinput touchpad catchall"
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) Using input driver 'libinput' for 'Apple Wireless Trackpad'
de juny 13 21:37:50 TM1703 upowerd[1271]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: got fd for /dev/input/event16 13:80 fd 65 paused 0
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: always reports core events
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "Device" "/dev/input/event16" (40,64 cm)˜
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "_source" "server/udev"
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: is tagged by udev as: Touchpad
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device is a touchpad
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/i
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) XINPUT: Adding extended input device "Apple Wireless Trackpad" (type: TOUCHPAD, id 11)
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "AccelerationScheme" "none"
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: (accel) selected scheme none/0
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: (accel) acceleration factor: 2.000
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: (accel) acceleration threshold: 4
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: is tagged by udev as: Touchpad
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device is a touchpad
de juny 13 21:37:51 TM1703 upowerd[1271]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/power_supply/hid-f4:1b:a1:3
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "65" (1,65 m)˜
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput"
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80
de juny 13 21:37:59 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed
de juny 13 21:37:59 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009
de juny 13 21:37:59 TM1703 kernel: magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
de juny 13 21:37:59 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
de juny 13 21:37:59 TM1703 kernel: magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device.
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file.
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16)
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "libinput touchpad catchall"
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) Using input driver 'libinput' for 'Apple Wireless Trackpad'
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: got fd for /dev/input/event16 13:80 fd 65 paused 0
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: always reports core events
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "Device" "/dev/input/event16" (40,64 cm)˜
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "_source" "server/udev"
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: is tagged by udev as: Touchpad
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device is a touchpad
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) XINPUT: Adding extended input device "Apple Wireless Trackpad" (type: TOUCHPAD, id 11)
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "AccelerationScheme" "none"
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: (accel) selected scheme none/0
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: (accel) acceleration factor: 2.000
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: (accel) acceleration threshold: 4
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: is tagged by udev as: Touchpad
de juny 13 21:37:59 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device is a touchpad
de juny 13 21:37:59 TM1703 upowerd[1271]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A
de juny 13 21:38:00 TM1703 upowerd[1271]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/power_supply/hid-f4:1b:a1:
lines 6761-6814/6814 (END)

In case it is useful, I am using blueman 2.0.5-1ubuntu1 and libinput-bin 1.10.4-1
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-10 (166 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp.
 Bus 001 Device 003: ID 04f3:0c1a Elan Microelectronics Corp.
 Bus 001 Device 002: ID 05c8:03a2 Cheng Uei Precision Industry Co., Ltd (Foxlink)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Timi TM1703
Package: linux (not installed)
ProcEnviron:
 LANG=ca_ES.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=e5e53ee1-0a10-48ee-8f7c-1d553ecc5607 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-52-generic N/A
 linux-backports-modules-4.15.0-52-generic N/A
 linux-firmware 1.173.6
Tags: bionic
Uname: Linux 4.15.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/11/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: XMAKB3M0P130D
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TM1703
dmi.board.vendor: Timi
dmi.board.version: XMAKB3M0P130D
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Timi
dmi.chassis.version: XMAKB3M0P130D
dmi.modalias: dmi:bvnInsydeCorp.:bvrXMAKB3M0P130D:bd09/11/2018:svnTimi:pnTM1703:pvrXMAKB3M0P130D:rvnTimi:rnTM1703:rvrXMAKB3M0P130D:cvnTimi:ct10:cvrXMAKB3M0P130D:
dmi.product.family: Timibook
dmi.product.name: TM1703
dmi.product.version: XMAKB3M0P130D
dmi.sys.vendor: Timi

whochismo (whochismo)
affects: ubuntu → libinput (Ubuntu)
whochismo (whochismo)
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The above log looks like a kernel issue (if not a hardware issue).

affects: libinput (Ubuntu) → linux (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1834085

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also, please try a newer kernel like:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.14/

or

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/

and tell us if either of those improve the situation.

Revision history for this message
whochismo (whochismo) wrote :

Hi,

apport-collect doesn't seem to work properly. After it gathers info about my installation, it asks me whether to send the report or not, and then it just closes.

I also tried using ubuntu-bug in the first place, but I had exactly the same problem. That's why I submitted the bug manually.

I will try these kernels. I just download and install the deb file, and then reboot, right?

Revision history for this message
whochismo (whochismo) wrote :

I tried the kernel v5.1.14, and the problem happened twice after 38 minutes, so no changes here.

I also tried installing the kernel v5.2-rc6, but there were several errors during the installation:

/etc/kernel/header_postinst.d/dkms:
ERROR (dkms apport): kernel package linux-headers-5.2.0-050200rc6-generic is not supported
Error! Bad return status for module build on kernel: 5.2.0-050200rc6-generic (x86_64)
Consult /var/lib/dkms/nvidia/418.56/build/make.log for more information.
ERROR (dkms apport): kernel package linux-headers-5.2.0-050200rc6-generic is not supported
Error! Bad return status for module build on kernel: 5.2.0-050200rc6-generic (x86_64)
Consult /var/lib/dkms/virtualbox/5.2.18/build/make.log for more information.
S'està configurant linux-modules-5.2.0-050200rc6-generic (5.2.0-050200rc6.201906222033)
S'està configurant linux-image-unsigned-5.2.0-050200rc6-generic (5.2.0-050200rc6.201906222033)
S'estan processant els activadors per a linux-image-unsigned-5.2.0-050200rc6-generic (5.2.0-050200rc6.201906222033)
/etc/kernel/postinst.d/dkms:
ERROR (dkms apport): kernel package linux-headers-5.2.0-050200rc6-generic is not supported
Error! Bad return status for module build on kernel: 5.2.0-050200rc6-generic (x86_64)
Consult /var/lib/dkms/nvidia/418.56/build/make.log for more information.
ERROR (dkms apport): kernel package linux-headers-5.2.0-050200rc6-generic is not supported
Error! Bad return status for module build on kernel: 5.2.0-050200rc6-generic (x86_64)
Consult /var/lib/dkms/virtualbox/5.2.18/build/make.log for more information.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.2.0-050200rc6-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Es genera un fitxer de configuració...
S'ha trobat una imatge de linux: /boot/vmlinuz-5.2.0-050200rc6-generic
s'ha trobat una imatge de initrd: /boot/initrd.img-5.2.0-050200rc6-generic
S'ha trobat una imatge de linux: /boot/vmlinuz-5.1.14-050114-generic
s'ha trobat una imatge de initrd: /boot/initrd.img-5.1.14-050114-generic
S'ha trobat una imatge de linux: /boot/vmlinuz-4.15.0-52-generic
s'ha trobat una imatge de initrd: /boot/initrd.img-4.15.0-52-generic
S'ha trobat una imatge de linux: /boot/vmlinuz-4.15.0-51-generic
s'ha trobat una imatge de initrd: /boot/initrd.img-4.15.0-51-generic
S'ha trobat Windows Boot Manager a /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done

Revision history for this message
whochismo (whochismo) wrote :

Ok, can confirm that the bug also occurs with the kernel v5.2-rc6 (which booted, despite showing some errors during startup). It appeared after 15 minutes of using it.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If this does not work for you:

  apport-collect 1834085

then instead please run:

  apport-cli -u 1834085

Revision history for this message
whochismo (whochismo) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
Revision history for this message
whochismo (whochismo) wrote : AudioDevicesInUse.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : CRDA.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : CurrentDmesg.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : IwConfig.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : Lspci.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : ProcInterrupts.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : ProcModules.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : RfKill.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : UdevDb.txt

apport information

Revision history for this message
whochismo (whochismo) wrote : WifiSyslog.txt

apport information

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please boot with kernel parameter "usbcore.dyndbg=+p", reproduce the issue and attach dmesg.

Revision history for this message
whochismo (whochismo) wrote :

I have experienced the issue at least once since I booted the computer.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Kernel parameter wasn't added:

Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=e5e53ee1-0a10-48ee-8f7c-1d553ecc5607 ro quiet splash vt.handoff=1

Revision history for this message
whochismo (whochismo) wrote :

Dammit. What is the correct way of adding it? When booting, at the grub menu, y selected my Ubuntu entry, and pressed 'e' to edit. Then there was a series of lines with instructions (I suppose), and I added another line with 'usbcore.dyndbg=+p'. Then I pressed F10 (if I recall correctly) to boot.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

To add kernel parameters permanently (and not needing the grub menu) you can add them to /etc/default/grub as part of the GRUB_CMDLINE_LINUX_DEFAULT line.

Revision history for this message
whochismo (whochismo) wrote :

I edited that line in /etc/default/grub so it reads:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.dyndbg=+p"

However, I don't see any changes in dmesg after I reboot:

[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=e5e53ee1-0a10-48ee-8f7c-1d553ecc5607 ro quiet splash vt.handoff=1

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry, I forgot to mention that after editing that file you need to run:

  sudo update-grub

Revision history for this message
whochismo (whochismo) wrote :
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
whochismo (whochismo) wrote :

I just tried it. The problem appeared when uptime was 56 minutes. I attach the output of dmesg in case it helps.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It looks like power management might be an issue.

Are you using powertop or 'tlp' to configure power management? If so then please try undoing your power management settings (or just uninstalling 'tlp').

Revision history for this message
whochismo (whochismo) wrote :

Yes, I was using tlp for power management (it's a laptop). I will try to disable it and report back.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in tlp (Ubuntu):
status: New → Incomplete
Revision history for this message
Raphaël Halimi (raph) wrote :

THIS IS NOT A BUG.

This is in TLP's FAQ :

https://linrunner.de/en/tlp/docs/tlp-faq.html#btusb

Please read the documentation, do what it says, confirm that your problem is fixed, and close the bug as invalid.

Revision history for this message
whochismo (whochismo) wrote :

I completely uninatalled tlp this morning and I am still experiencing this issue.

I don't think it has anything to do with it.

(As I mentioned previously, other bluetooth devices work alright, even with tlp).

Revision history for this message
Raphaël Halimi (raph) wrote :

Did you reboot your machine after uninstalling TLP ?

Revision history for this message
whochismo (whochismo) wrote :

Yes, I have turned it off an on several times during the day.

But give me a couple of days and I will check (and attach) the corresponding logs.

no longer affects: tlp (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
whochismo (whochismo) wrote :

Hi again, I have been away for a few days. I have been trying now, after having uninstalled tlp the other day (and making sure it is indeed the case), and using the kernel 5.2.0-050200rc7-generic #201906300430, I have experienced the issue at the 13 minute mark.

I have attached the output of the dmesg command in case it could be useful.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please raise the issue to upstream, i.e. mail to <email address hidden>.

Revision history for this message
whochismo (whochismo) wrote :

Any news, or any workaround I could try?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please report the bug to the kernel developers at the above address in comment #40, or at https://bugzilla.kernel.org/. Then let us know the new bug ID.

Revision history for this message
In , marcpalaus (marcpalaus-linux-kernel-bugs) wrote :

Hello.

I initially reported this bug to Ubuntu's bugtracking system, and from there I was redirected here.

This is the initial bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834085

Basically the bug is described in the bug report above, together with several log files. I have an Apple Magic Trackpad 2 connected via bluetooth which constantly disconnects and reconnects after a few secons, and I don't think it has to do with the bluetooth module in my computer, as other bluetooth devices work just fine.

I have experienced this issue in kernels v4.15.0-58-generic, v5.1.14 and v5.2-rc6.

Tell me if you need more information I should provide.

Thanks in advance.

Revision history for this message
whochismo (whochismo) wrote :

Ok, I reported the bug in the kernel.org bugtracking system. It's this one: https://bugzilla.kernel.org/show_bug.cgi?id=204589

(Back in the day I sent an email to that address, but I never received a response).

Revision history for this message
Niels Peen (nielspeen) wrote :

Had the same issue with my Magic Trackpad. After reading this possibly related bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113 I decided to disable upower:

systemctl stop upower
systemctl disable upower

This works around the problem for me.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I don't think that's recommended. As I understand it, disabling upower means to disable the power management for the entire machine :)

Revision history for this message
Niels Peen (nielspeen) wrote :

You can still do power management using any non-gnome power management tool. Somewhat annoying indeed, but less so than losing my trackpad every hour ;-)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please try adding kernel parameter:

  btusb.enable_autosuspend=0

(copied from bug 1801642)

Revision history for this message
whochismo (whochismo) wrote :

Hey, adding that parameter to /etc/default/grub seemed to work! I have not had a single disconnection for more than three hours now.

Revision history for this message
whochismo (whochismo) wrote :

Ok, let me share my experience a day later. At more than 7 hours of being in my computer, I suffered a disconnection. Another one followed maybe one or two hours later. This is, however, a big improvement over the past situation, where there was one disconnection every 30 or 40 minutes. so maybe these two disconnections I suffered yesterday were caused by something else.

Revision history for this message
whochismo (whochismo) wrote :

I just suffered three disconnections during the last hour, so it seems that the problem is still there, and when they happen, it's a matter of luck.

(And yes, I made sure that btusb.enable_autosuspend=0 was in the kernel)

[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUI
D=e5e53ee1-0a10-48ee-8f7c-1d553ecc5607 ro quiet splash usbcore.dyndbg=+p btusb.e
nable_autosuspend=0 vt.handoff=1

I have not tried disabling upower yet.

Revision history for this message
whochismo (whochismo) wrote :

Ok, can confirm that disabling upower (via the commands in comment #44) does not help. I suffered another disconnection when the uptime was close to 4 hours.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , oftrupert1928 (oftrupert1928-linux-kernel-bugs) wrote :

Just to note that I have exactly the same issue, Apple Magic Trackpad 1 on Ubuntu 18.04 LTS, kernel 5.3.0-42-generic.

Happy to provide more info as needed.

Revision history for this message
satmandu (satadru-umich) wrote :

I think this is the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113

has anybody submitted this upstream to the linux-input mailing list yet?

It's definitely happening with 5.4.0-23-lowlatency on focal beta and my magicmouse trackpad.

I will try with a mainline kernel next...

Revision history for this message
satmandu (satadru-umich) wrote :

Definitely still get the error message, at least right at first connection, using mainline 5.6.3 on focal beta:
 magicmouse *:*:*:*: unknown main item tag 0x0

Revision history for this message
satmandu (satadru-umich) wrote :

Definitely still seeing this, but over 12 hours later I can immediately use the devices again in mainline 5.6.3.

dmesg | grep 'magic\|apple'
[68065.162639] apple *:*:*.*: unknown main item tag 0x0
[68065.163407] apple *:*:*.*: input,hidraw5: BLUETOOTH HID v0.50 Keyboard [satadru’s keyboard] on *:*:*:*:*:*
[68086.650551] magicmouse *:*:*.*: unknown main item tag 0x0
[68086.650753] magicmouse *:*:*.*: input,hidraw6: BLUETOOTH HID v1.60 Mouse [satadru's Trackpad] on *:*:*:*:*:*

Revision history for this message
whochismo (whochismo) wrote :

I can confirm that the problem persists on a clean install of Ubuntu 20.04 LTS (kernel 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64).

Revision history for this message
In , marcpalaus (marcpalaus-linux-kernel-bugs) wrote :

The problem persists on a clean install of Ubuntu 20.04, kernel 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64.

Revision history for this message
In , marcpalaus (marcpalaus-linux-kernel-bugs) wrote :

I would like to make a correction to the original post. The device that has this problem is an Apple Magic Trackpad 1, not 2. It's the one that is roughly square in shape and uses AA batteries instead of a rechargeable one.

You-Sheng Yang (vicamo)
tags: added: hwe-bluetooth hwe-touchpad
Revision history for this message
Kimberly Tran (kayjtea) wrote :

Disabling upower isn't enough -- it will start up again when an app (such as your browser) requires power management support. You have to uinstall upower from your system. (Note that this will make some apps, such as steam, unstable.)

This bug started happening when I switched out my wifi card. I have a Dell XPS 9560. My Magic Mouse only started having these disconnect issues after I switched to an Intell 9260 card. I might switch back to Killer card to verify.

I caught upower doing its (bad) thing just now, after being started up by brave browser.

Apr 26 22:21:21 nodoubt dbus-daemon[833]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.2664' (uid=1000 pid=15830 comm="/usr/lib/brave/brave ")
Apr 26 22:21:21 nodoubt systemd[1]: Starting Daemon for power management...
Apr 26 22:21:23 nodoubt dbus-daemon[833]: [system] Successfully activated service 'org.freedesktop.UPower'
Apr 26 22:21:23 nodoubt systemd[1]: Started Daemon for power management.
Apr 26 22:26:14 nodoubt bluetoothd[831]: Can't get HIDP connection info
Apr 26 22:26:15 nodoubt kernel: magicmouse 0005:05AC:030D.000D: unknown main item tag 0x0

Magic mouse is now disconnected.

If I completely uninstall upower, the problem goes away.

Revision history for this message
Luke Midworth (areographe) wrote :

I'm on kernel 5.8.8 and am experiencing what I think is the exact same issue with my Magic Trackpad 1

Revision history for this message
In , areluno (areluno-linux-kernel-bugs) wrote :

Just to confirm... The problem unfortunately still persists on a clean install of Ubuntu 20.10, kernel 5.8.0-36-generic #40-Ubuntu SMP Tue Jan 5 21:54:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
In , andrenbrandao (andrenbrandao-linux-kernel-bugs) wrote :

I am having the same problem with an Apple Magic Trackpad 2, Ubuntu 20.04 and kernel 5.8.0-41-generic #46~20.04.1-Ubuntu SMP.

Revision history for this message
André Brandão (andrenbrandao) wrote :

I am having the same problem with an Apple Magic Trackpad 2, Ubuntu 20.04 and kernel 5.8.0-41-generic #46~20.04.1-Ubuntu SMP.

[462154.113890] magicmouse 0005:004C:0265.00CE: unknown main item tag 0x0
[462154.114012] input: Apple Inc. Magic Trackpad 2 as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.0/bluetooth/hci0/hci0:768/0005:004C:0265.00CE/input/input253
[462154.114248] magicmouse 0005:004C:0265.00CE: input,hidraw2: BLUETOOTH HID v1.02 Mouse [André Brandão’s Trackpad] on 04:6c:59:0e:14:fa

Revision history for this message
Mike Jones (mike-jones) wrote :

I'm having the same issues on my Dell Precision laptop with 20.04 lts, kernel 5.8.0-43.

One thing I've noticed: it seems to happen less frequently with Wayland than with X.

Revision history for this message
Bas (bas-kin) wrote :

exactly the same issue on Ubuntu 20.04 5.8.0-50 on a Lenovo X1 gen8 with Magic Tracpad 2

Revision history for this message
Jose Rojas (j-rojas) wrote :

Same issue on Ubuntu 20.04 5.11.0 with an Apple Magic Trackpad on an AMD desktop machine. My Apple Bluetooth keyboard works great - no issues with any disconnections. The Apple Magic Trackpad will glitch typically when there is some significant CPU load. The glitch will either disconnect the trackpad entirely, or it reconnects after 10 to 60 seconds but usually in a state where the normal tap is registered as a secondary click. The trackpad works great with my Apple laptop so this is not a hardware issue.

Revision history for this message
lorn10 (kle) wrote :

Hi to all!
I can unfortunately confirm this "unknown main item tag 0x0" error also for Kubuntu 20.04 and kernel 5.11.0-27. The used hardware is an Apple Magic Mouse 2 at an iMac8,1. It should be noted that Kubuntu is running in native (U)EFI mode, not in legacy CSM Bios-emulation. Maybe this fact has here some relevance. The coresponding dmesg output regarding this issue looks as follows:

[ 90.797431] hid-generic 0005:004C:0269.0007: unknown main item tag 0x0
[ 90.797529] input: Franzs Maus Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2.3/5-2.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0007/input/input12
[ 90.797780] input: Franzs Maus as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2.3/5-2.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0007/input/input13
[ 90.797871] hid-generic 0005:004C:0269.0007: input,hidraw3: BLUETOOTH HID v0.70 Mouse [Franzs Maus] on 60:f8:1d:ad:62:e1
[ 90.873387] magicmouse 0005:004C:0269.0007: unknown main item tag 0x0
[ 90.873514] input: Franzs Maus as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2.3/5-2.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0007/input/input14
[ 90.873768] magicmouse 0005:004C:0269.0007: input,hidraw3: BLUETOOTH HID v0.70 Mouse [Franzs Maus] on 60:f8:1d:ad:62:e1
[ 90.973119] hid-generic 0005:004C:0269.0007: unknown main item tag 0x0
[ 90.973202] input: Franzs Maus Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2.3/5-2.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0007/input/input15
[ 90.973321] input: Franzs Maus as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2.3/5-2.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0007/input/input16
[ 90.973390] hid-generic 0005:004C:0269.0007: input,hidraw3: BLUETOOTH HID v0.70 Mouse [Franzs Maus] on 60:f8:1d:ad:62:e1
[ 93.041395] magicmouse 0005:004C:0269.0007: unknown main item tag 0x0
[ 93.041508] input: Franzs Maus as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2.3/5-2.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0007/input/input17
[ 93.041685] magicmouse 0005:004C:0269.0007: input,hidraw3: BLUETOOTH HID v0.70 Mouse [Franzs Maus] on 60:f8:1d:ad:62:e1

Revision history for this message
In , heavy (heavy-linux-kernel-bugs) wrote :

I had been experiencing this same issue with a Magic Trackpad 2 on the past several releases of Fedora. My workaround was simply to plug in my trackpad with a USB cable. After upgrading to Fedora 35, I tried using bluetooth again and it seemed to be working fine for a week or so, but it is back to disconnecting regularly, so I've switched back to a wired approach.

Revision history for this message
Keiland Cooper (kwcooper) wrote (last edit ):

Hi folks. Just want to chime in that I also have the same issue on the 22.04 beta with the magic trackpad 1, where it disconnects at random intervals. I found some old posts around, some dating back to 2015 with the same issue... no dice with most of their proposed solutions.

- Issue persists with both the internal Bluetooth adapter and a dongle.

- I seem to not have the issue with the apple magic mouse, surprisingly

- disabling upower doesn't seem to help, and just makes the system unstable.

- In `sudo btmon` I often see an HCI event mode change at random intervals to exit sniffing. However, when the trackpad disconnects, I see a HCI event mode change reporting a connection timeout (0x08).

A lot of the suggested fixes do have power settings in common, though it seems. But disabling power or suspend would either lead to, at best, a lot of battery changes, or at worst, an unstable system like I have seen.

Revision history for this message
Zealotous (zealotous) wrote :

Hi Guys, I also have the same issue on Lenovo P14s Gen1 internal Bluetooth adapter Intel AX201.

The trackpad and/or a bluetooth keyboard keeps disconnecting.

Disconnects are more frequent/probable
when I'm using bluetooth headphones (Bose QC 35 II) in headset mode.

I cannot conferm that an usb dongle has the issue.
11 euro RTL8761B dongle with a big antenna has no issues.

Zexmte BT-506 works perfectly with 3 devices connected simultaniously.

```
root@pop-os:~# lsusb | grep Bluetooth
Bus 001 Device 023: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth 5.1 Radio
Bus 001 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth

root@pop-os:~# uname -a
Linux pop-os 5.17.5-76051705-generic #202204271406~1651504840~22.04~63e51bd SMP PREEMPT Mon May 2 15: x86_64 x86_64 x86_64 GNU/Linux
```

Revision history for this message
In , andri (andri-linux-kernel-bugs) wrote :

I know this bug is about the Magic Trackpad, but just in case they're related, I'm experiencing the same drops with multiple ca 2010–2012 Apple Magic Mouse products.

This with two different computers, kernel versions and BT chipsets:
- Arch Linux LTS v5.15.38-1-lts and Intel Corp. Wireless-AC 3168 Bluetooth
- Fedora v5.17.13-300.fc36.x86_64 and Intel Corp. AX201 Bluetooth (linux-firmware @ 20220610)

There's definitely something reproducible. The common suggestion to disable eSCO does not help.

I also noticed another possibly related issue: https://bugzilla.kernel.org/show_bug.cgi?id=103631

Revision history for this message
In , heavy (heavy-linux-kernel-bugs) wrote :

And it is still happening for me on Fedora 36. Same experience as before, where it seemed to be working better initially after upgrading, but after some time/updates it is back to being very spotty. I'm not sure if this is my imagination or not, but I always get my hopes up that it is fixed, only to have them dashed.

Revision history for this message
Clarence Bomfink (clapers) wrote :

This is the only thing that has managed to (semi-)permanently solve the issue for me:

https://bugzilla.kernel.org/show_bug.cgi?id=103631

I spent many hours recompiling the kernel to get months of blissful disconnection-free use, only for the patch to be removed after a kernel update :(

I can't face recompiling the kernel every time, so if anyone can build a solution based on this, I'd love to know about it.

I actually like the trackpad enough to switch distro if anyone has used one that works out of the box?

Revision history for this message
ALEKSEY SCHERBAKOV (scherbakoff) wrote :

The same problem with disabling the apple magic trackpad with a connection to the bluetooth adapter built into the computer. Ubuntu 22.04. But I connected an external dongle. Installed Blueman Bluetooth Manager. The system wanted to connect to the trackpad via the bluetooth adapter built into the computer, but in the installed manager, I deleted the connection via the built-in adapter and connected via an external dongle. Since then, the trackpad has been disabled only once in many days. It may not solve the problem, but it does reduce it quite a bit. I hope this will be resolved in the future!

Revision history for this message
Pedro A. Aranda (paaguti-p) wrote :

Continues to happen (2023-01-08) on

Linux paag-elitebook-840g2 5.15.0-57-generic #63-Ubuntu SMP Thu Nov 24 13:43:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

A pity this isn't included in the kernel patches Ubuntu applies. It happens for every since Bluetooth mouse I have tested! Not just on Apple's trackpads, magic or not!

Revision history for this message
In , queeup (queeup-linux-kernel-bugs) wrote :

Created attachment 303579
my systems dmesg.log

This is fedora silverblue 36 dmesg. Last lines have some disconnect info

Revision history for this message
In , queeup (queeup-linux-kernel-bugs) wrote :

Created attachment 303580
journalctl -fu bluetooth > journalctl-bluetooth.log

print out of fedora silverblue 36 bluetooth service debug

journalctl -fu bluetooth > journalctl-bluetooth.log

Revision history for this message
In , queeup (queeup-linux-kernel-bugs) wrote :

Created attachment 303581
btmon -p 7 -i hci0 -w hcidump

This is BTSnoop file. Collected disconnection errors.

file hcidump
hcidump: BTSnoop version 1

Revision history for this message
In , queeup (queeup-linux-kernel-bugs) wrote :
Download full text (6.6 KiB)

```
$ lspci -nnk | grep 0280 -A3
03:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
 Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

$ lsusb -d 8087:
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ bluetoothctl info
Device 84:FC:FE:E0:A5:F0 (public)
 Alias: Apple Magic Trackpad
 Class: 0x00002594
 Icon: input-tablet
 Paired: yes
 Bonded: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 WakeAllowed: yes
 LegacyPairing: yes
 UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 Modalias: usb:v05ACp030Ed0160

$ uname -a
Linux fedora 5.19.6-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 31 17:58:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="36.20220902.0 (Silverblue)"
ID=fedora
VERSION_ID=36
VERSION_CODENAME=""
PLATFORM_ID="platform:f36"
PRETTY_NAME="Fedora Linux 36.20220902.0 (Silverblue)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:36"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora-silverblue/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=36
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=36
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Silverblue"
VARIANT_ID=silverblue
OSTREE_VERSION='36.20220902.0'

$ rpm -qa linux-firmware iwlax2xx-firmware bluez
bluez-5.65-1.fc36.x86_64
iwlax2xx-firmware-20220815-138.fc36.noarch
linux-firmware-20220815-138.fc36.noarch

$ dmesg | grep firmware
[ 3.059539] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 7.048785] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 7.101611] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 7.181529] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-72.ucode failed with error -2
[ 7.242302] iwlwifi 0000:03:00.0: loaded firmware version 71.058653f6.0 cc-a0-71.ucode op_mode iwlmvm
[ 8.865213] Bluetooth: hci0: Waiting for firmware download to complete

$ dmesg | grep Bluetooth
[ 6.876698] Bluetooth: Core ver 2.22
[ 6.876723] Bluetooth: HCI device and connection manager initialized
[ 6.876727] Bluetooth: HCI socket layer initialized
[ 6.876728] Bluetooth: L2CAP socket layer initialized
[ 6.876734] Bluetooth: SCO socket layer initialized
[ 7.047790] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 7.048779] Bluetooth: hci0: Device revision is 1
[ 7.048781] Bluetooth: hci0: Secure boot is enabled
[ 7.048782] Bluetooth: hci0: OTP lock is enabled
[ 7.048783] Bluetooth: hci0: API lock is enabled
[ 7.048784] Bluetooth: hci0: Debug lock is disabled
[ 7.048785] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 7.101611] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 7.101745] Bluetooth: hci0: Boot Address:...

Read more...

Revision history for this message
Özgür Baskin (ozgur-baskin) wrote :

Fedora 37 Silverblue and Intel AX200 bluetooth, I have same problem with Apple Magic Trackpad V1 (05AC:030E)

Revision history for this message
ALEKSEY SCHERBAKOV (scherbakoff) wrote :

I notice that the trackpad's power graph is not smooth, but dips. When there are drawdowns on the chart, then at such a time, trackpad disconnections are more common. When connected after a break, the trackpad blinks the connection light.

Revision history for this message
Pedro (pedrobth) wrote :

I have the same issue with trackpad 1 and hp victus laptop running ubuntu 22.04.2

Revision history for this message
Miguel Forero (miguelforero) wrote (last edit ):

I have the same issue. I use generic bluetooth keyboard, Apple trackpad and bluetooth headphones, 3 devices, I connect all three without problem, only the Apple trackpad problem. But when I activate google meet, the apple trackpad disconnects every 10 seconds or less, I have to disconnect the headphones from the bluetooh. A rather unusual problem.

System76 Galago Pro with Pop OS 22.04 LTS

Revision history for this message
ALEKSEY SCHERBAKOV (scherbakoff) wrote :

There are oddities in the food schedule:

https://ibb.co/28JzH4h
https://ibb.co/6JQtBPj

Revision history for this message
In , scherbakov.al (scherbakov.al-linux-kernel-bugs) wrote :

I have the same problem on ubuntu 23.04.
My report: https://pastebin.com/3A9EXusp

Revision history for this message
ALEKSEY SCHERBAKOV (scherbakoff) wrote :
Revision history for this message
In , scherbakov.al (scherbakov.al-linux-kernel-bugs) wrote :

New error messages when communication is lost with Magic Trackpad:
I booted Ubuntu 23.04(kernel 6.2.0) from a flash drive - the same error:
https://pastebin.com/5KtUjCHQ
I booted from Fedor's(kernel 6.2.9) flash drive - error:
https://pastebin.com/4LJC7NJQ
When using Fedora, communication breaks also occur.

Revision history for this message
ALEKSEY SCHERBAKOV (scherbakoff) wrote :

New error messages when communication is lost with Magic Trackpad:
I booted Ubuntu 23.04(kernel 6.2.0) from a flash drive - the same error:
https://pastebin.com/5KtUjCHQ
I booted from Fedor's(kernel 6.2.9) flash drive - error:
https://pastebin.com/4LJC7NJQ
When using Fedora, communication breaks also occur.

Revision history for this message
ALEKSEY SCHERBAKOV (scherbakoff) wrote :

I found this answer from Vudentz on github :

Looks like it is a link layer issue as the connection just times out when we attempt to exit sniff mode:

HCI Event: Disconnect Complete (0x05) plen 4 #18605 [hci0] 358.578948
Status: Success (0x00)
Handle: 256
Reason: Connection Timeout (0x08)

Perhaps the device doesn't like that we are exitting sniff mode on our own or something like that.

Revision history for this message
In , scherbakov.al (scherbakov.al-linux-kernel-bugs) wrote :

I found this answer from Vudentz on github :

Looks like it is a link layer issue as the connection just times out when we attempt to exit sniff mode:

HCI Event: Disconnect Complete (0x05) plen 4 #18605 [hci0] 358.578948
Status: Success (0x00)
Handle: 256
Reason: Connection Timeout (0x08)

Perhaps the device doesn't like that we are exitting sniff mode on our own or something like that.

Revision history for this message
In , attila (attila-linux-kernel-bugs) wrote :

i'm also affected by this for years, and it makes the touchpad rather annoying to use.

it's been happening on different laptops, but my current setup is:

Thinkpad Carbon X1 gen6
Linux 6.4.16
x86_64
running Guix

$ lspci -nnk | grep 0280 -A3
02:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
 Subsystem: Intel Corporation Dual Band Wireless-AC 8265 [8086:0010]
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

$ lsusb -d 8087:
Bus 001 Device 015: ID 8087:0a2b Intel Corp. Bluetooth wireless interface

$ bluetoothctl info
Device 28:37:37:2D:43:AD (public)
 Alias: 28-37-37-2D-43-AD
 Class: 0x00002594
 Icon: input-tablet
 Paired: yes
 Bonded: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 WakeAllowed: yes
 LegacyPairing: no
 UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 Modalias: usb:v05ACp030Ed0160

dmesg at every dis-/reconnect:

[364555.042486] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:512/0005:05AC:030E.009C/input/input166
[364555.042732] magicmouse 0005:05AC:030E.009C: input,hidraw5: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 84:fd:d1:8d:7a:e7
[366309.985739] magicmouse 0005:05AC:030E.009D: unknown main item tag 0x0
[366309.985887] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.009D/input/input167
[366309.986256] magicmouse 0005:05AC:030E.009D: input,hidraw5: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 84:fd:d1:8d:7a:e7
[366513.879351] magicmouse 0005:05AC:030E.009E: unknown main item tag 0x0
[366513.879540] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.009E/input/input168

Revision history for this message
Özgür Baskin (ozgur-baskin) wrote :

Happy to report, my problem solved with Gnome 45.1 & Fedora 39. No disconnect or freeze with apple trackpad.

Fedora 39 Silverblue
Intel AX200 bluetooth
Apple Magic Trackpad V1 (05AC:030E)

```
$ uname -r
6.6.3-200.fc39.x86_64

$ rpm -qa iwlwifi*
iwlwifi-dvm-firmware-20231111-1.fc39.noarch
iwlwifi-mvm-firmware-20231111-1.fc39.noarch
```

Revision history for this message
In , queeup (queeup-linux-kernel-bugs) wrote :

Happy to report, my problem solved with Gnome 45.1 & Fedora 39. No disconnect or freeze with apple trackpad.

Fedora 39 Silverblue
Intel AX200 bluetooth
Apple Magic Trackpad V1 (05AC:030E)

```
$ uname -r
6.6.3-200.fc39.x86_64

$ rpm -qa iwlwifi*
iwlwifi-dvm-firmware-20231111-1.fc39.noarch
iwlwifi-mvm-firmware-20231111-1.fc39.noarch

```

Revision history for this message
In , scherbakov.al (scherbakov.al-linux-kernel-bugs) wrote :

I tested it. The trackpad worked for more than an hour without the same disconnections every 10 minutes that we had before. But an hour later it disconnected and could not restore the connection. Only restarting bluetooth helped. This happened several times. The problem has not yet been resolved. Fedora 39.

Revision history for this message
In , heavy (heavy-linux-kernel-bugs) wrote :

Unfortunately, I think the issue is still not resolved. The touchpad still disconnects for me on a fully updated Fedora 39 with Gnome 45.2.

Revision history for this message
Lee Fleming (leefleming) wrote :

I started having this problem today. I'm not on ubuntu I'm on suse tumbleweed.
I'm posting this here because it was the 1st google hit and it might help
someone. I can reproduce this problem.

I have an LG Xboom external bluetooth speaker. My magic trackpad will stop
responding when the speaker is on, connected and also plugged into the USB to
charge it. When I stop moving the mouse pointer for 5 seconds the trackpad
disconnects. It also only happens when the speaker is connected to the USB A
port. (13inch AMD framework laptop).

If I instead connect the speaker to the USB C port then the disconnects stop
happening.

Revision history for this message
In , LeeFlemingster (leeflemingster-linux-kernel-bugs) wrote :

I have been able to reproduce this problem.

OpenSuse Tumbleweed.
Framework AMD 13-inch laptop.

I've only seen the magic trackpad 2 disconnect under a specific condition.

I have an LG Xboom bluetooth speaker. When the speaker is on, connected to
bluetooth and connected to USB to charge, then when I stop moving the mouse
pointer for 5 seconds the trackpad disconnects.

This only happens when the speaker is connected to the USB A port (front left).
If connected to the USB C port (or physically disconnected entirely) then the
problem goes away.

I have not tried swaping the USB modules on this laptop. Not all the ports are
made equal. The speaker was connected to port 2 in this diagram. https://knowledgebase.frame.work/en_us/expansion-card-functionality-on-framework-laptop-13-amd-ryzen-7040-series-SkrVx7gAh

Revision history for this message
In , LeeFlemingster (leeflemingster-linux-kernel-bugs) wrote :

I did some more testing. It doesn't matter if the speaker is attached to USB A
or USB C. The problem is seen when the speaker is attached to USB 3.2 and not
seen when attached to USB 4 (see diagram in last post).

I did the following testing.
Speaker connected to port 2 USB A. Trackpad disconnects.
Speaker connected to port 2 USB C. Trackpad disconnects.
Speaker connected to port 1 USB C. No disconnect.
Speaker connected to port 3 USB C. No disconnect.
Speaker connected to port 4 USB C. Trackpad disconnects.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.