- Arch-general - lists.archlinux.org

[arch-general] Segmentation fault when trying to install a self-created package
by Peter Nabbefeld 20 Dec '20

20 Dec '20

Hello, as the meshroom builds (from AUR) don't work for me, I tried to create my own package by modifying the PKGBUILD file of the meshroom-git package. This results in two issues: 1. While creating the package using makepkg, the whole git repository is downloaded - that's okay, of course. But all built artifacts seem to be contained in the resulting package file. As a git build shouldn't be "static": How can I create a build file for automatic downloading and building from current repository? 2. When installing the created package (pacman -U) and trying to start Meshroom, I get: "Segmentation fault (core dumped)". It seems, there's a problem with Meshroom's private shiboken2 installation: PID: 135087 (Meshroom) UID: 1000 (peter) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Sun 2020-12-20 11:04:25 CET (24min ago) Command Line: Meshroom Executable: /usr/lib/Meshroom-2020.1.1/Meshroom Control Group: /user.slice/user-1000.slice/session-9.scope Unit: session-9.scope Slice: user-1000.slice Session: 9 Owner UID: 1000 (peter) Boot ID: 4e5fb788a5324cd1b31363dee2d7b62e Machine ID: b1efa5af7b174c44adc4ec7990c10ad7 Hostname: tuchola Storage: /var/lib/systemd/coredump/core.Meshroom.1000.4e5fb788a5324cd1b31363dee2d7b62e.135087.1608458665000000.zst Message: Process 135087 (Meshroom) of user 1000 dumped core. Stack trace of thread 135087: #0 0x00007ff37636becb SbkObject_TypeF (libshiboken2.abi3.so.5.15 + 0xeecb) #1 0x00007ff37636d80d _ZN8Shiboken4initEv (libshiboken2.abi3.so.5.15 + 0x1080d) #2 0x00007ff37637fa79 _ZN8Shiboken6Module6createEPKcPv (libshiboken2.abi3.so.5.15 + 0x22a79) #3 0x00007ff3765b13e7 PyInit_shiboken2 (shiboken2.abi3.so + 0x23e7) #4 0x000055d17af0edfd n/a (Meshroom + 0x21adfd) #5 0x000055d17ae323c1 n/a (Meshroom + 0x13e3c1) #6 0x000055d17ae263b2 _PyEval_EvalFrameDefault (Meshroom + 0x1323b2) #7 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #8 0x000055d17ae31b6e _PyFunction_Vectorcall (Meshroom + 0x13db6e) #9 0x000055d17ae251ae _PyEval_EvalFrameDefault (Meshroom + 0x1311ae) #10 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #11 0x000055d17ae20dcf _PyEval_EvalFrameDefault (Meshroom + 0x12cdcf) #12 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #13 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #14 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #15 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #16 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #17 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #18 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #19 0x000055d17ae311b5 n/a (Meshroom + 0x13d1b5) #20 0x000055d17ae4587c _PyObject_CallMethodIdObjArgs (Meshroom + 0x15187c) #21 0x000055d17ae44dfd PyImport_ImportModuleLevelObject (Meshroom + 0x150dfd) #22 0x000055d17ae2393a _PyEval_EvalFrameDefault (Meshroom + 0x12f93a) #23 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #24 0x000055d17ae1efd1 _PyEval_EvalCodeWithName (Meshroom + 0x12afd1) #25 0x000055d17aee0a13 PyEval_EvalCode (Meshroom + 0x1eca13) #26 0x000055d17aee8023 n/a (Meshroom + 0x1f4023) #27 0x000055d17ae323c1 n/a (Meshroom + 0x13e3c1) #28 0x000055d17ae263b2 _PyEval_EvalFrameDefault (Meshroom + 0x1323b2) #29 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #30 0x000055d17ae31b6e _PyFunction_Vectorcall (Meshroom + 0x13db6e) #31 0x000055d17ae251ae _PyEval_EvalFrameDefault (Meshroom + 0x1311ae) #32 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #33 0x000055d17ae20dcf _PyEval_EvalFrameDefault (Meshroom + 0x12cdcf) #34 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #35 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #36 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #37 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #38 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #39 0x000055d17ae311b5 n/a (Meshroom + 0x13d1b5) #40 0x000055d17ae4587c _PyObject_CallMethodIdObjArgs (Meshroom + 0x15187c) #41 0x000055d17ae44dfd PyImport_ImportModuleLevelObject (Meshroom + 0x150dfd) #42 0x000055d17ae2393a _PyEval_EvalFrameDefault (Meshroom + 0x12f93a) #43 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #44 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #45 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #46 0x000055d17ae1efd1 _PyEval_EvalCodeWithName (Meshroom + 0x12afd1) #47 0x000055d17aee0a13 PyEval_EvalCode (Meshroom + 0x1eca13) #48 0x000055d17aee8023 n/a (Meshroom + 0x1f4023) #49 0x000055d17ae323c1 n/a (Meshroom + 0x13e3c1) #50 0x000055d17ae263b2 _PyEval_EvalFrameDefault (Meshroom + 0x1323b2) #51 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #52 0x000055d17ae31b6e _PyFunction_Vectorcall (Meshroom + 0x13db6e) #53 0x000055d17ae251ae _PyEval_EvalFrameDefault (Meshroom + 0x1311ae) #54 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #55 0x000055d17ae20dcf _PyEval_EvalFrameDefault (Meshroom + 0x12cdcf) #56 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #57 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #58 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #59 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #60 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13 Does somebody have an idea, what I could change? Kind regards, peter

1 0

[arch-general] Bug with CIFS mount
by Tasnad Kernetzky 17 Dec '20

17 Dec '20

Hi All, I suppose I hit this bug: https://bugs.archlinux.org/task/68963 and it seems it is not fully resolved. I didn't request to reopen the bug, because I'm not 100% sure it is really the same thing. I have a setup with kerberos/sssd/pam/autofs, authenticating with an active directory, and cifs mounts stopped working. Login and nfs with kerberos work fine, to the issue is quite likely with cifs. Mounting the cifs share works with libcap-ng-0.8-1, but not with libcap-ng-0.8.2-1. I have cifs-utils 6.11-2, sssd 2.4.0-2 and krb5 1.18.2-1. Did I miss something or am I hitting something special due to the setup? Does anybody have a clue what could be the issue? I include lots of details about the config and logs, but tl;dr: "mount -t cifs -o domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 //nas.example.com/theUser /nas/home/theUser" fails with "cifs.upcall[532824]: drop_all_capabilities: Unable to apply capability set: Success" Best, Tasnad Substituted values ================== * myMachine: the client's hostname (not fqdn) * theUser: the nonroot user trying to mount via autofs * 1234567: uid of theUser (from Active directory) * DOM: the AD domain * DOM.EXAMPLE.COM: domain, fqdn /etc/krb5.conf ============== [libdefaults] default_realm = DOM.EXAMPLE.COM udp_preference_limit = 0 default_ccache_name = FILE:/tmp/krb5cc_%{uid} dns_lookup_realm = true dns_lookup_kdc = true rdns = false ticket_lifetime = 10h renew_lifetime = 7d forwardable = true sssd.conf ========= [sssd] config_file_version = 2 domains = DOM.EXAMPLE.COM services = nss, pam [nss] default_shell = /bin/bash shell_fallback = /bin/bash filter_groups = root filter_users = root [domain/DOM.EXAMPLE.COM] id_provider = ad auth_provider = ad access_provider = simple ldap_schema = ad sudo_provider = none cache_credentials = false krb5_store_password_if_offline = false dyndns_update = false ldap_id_mapping = false use_fully_qualified_names = false enumerate = false ignore_group_members = true case_sensitive = preserving ad_enable_gc = false ad_hostname = myMachine ldap_search_base = [...] ldap_user_search_base = [...] ldap_user_search_scope = [...] ldap_group_search_base = [...] ldap_group_search_scope = [...] nsswitch.conf ============= passwd: files sss group: files sss shadow: files sss gshadow: files sss publickey: files hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns networks: files protocols: files services: files sss ethers: files rpc: files netgroup: files sss automount: sss homes.autofs ============ /nas/home /etc/autofs/auto.master.d/home.map -domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl home.map ======== * -username=$USER,cruid=$UID,vers=3.0 ://nas.example.com/& cifs idmap plugin ============ /etc/cifs_utils/idmap-plugin -> /usr/lib/cifs-utils/cifs_idmap_sss.so klist ===== Ticket cache: FILE:/tmp/krb5cc_<uid> Default principal: theUser(a)DOM.EXAMPLE.COM Valid starting Expires Service principal 12/16/2020 11:31:48 12/16/2020 21:25:18 krbtgt%2FDOM.EXAMPLE.COM(a)DOM.EXAMPLE.COM renew until 12/23/2020 11:25:18 automount -fd ============= handle_packet: type = 3 handle_packet_missing_indirect: token 727, name theUser, request pid 532818 attempting to mount entry /nas/home/theUser lookup_mount: lookup(file): looking up theUser lookup_mount: lookup(file): theUser -> -username=$USER,cruid=$UID,vers=3.0 ://nas.example.com/& parse_mount: parse(sun): expanded entry: -username=theUser,cruid=1234567,vers=3.0 ://nas.example.com/theUser parse_mount: parse(sun): gathered options: domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 parse_mount: parse(sun): dequote("://nas.example.com/theUser") -> ://nas.example.com/theUser parse_mount: parse(sun): core of entry: options=domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0, loc=://nas.example.com/theUser sun_mount: parse(sun): mounting root /nas/home, mountpoint theUser, what //nas.example.com/theUser, fstype cifs, options domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 do_mount: //nas.example.com/theUser /nas/home/theUser type cifs options domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 using module generic mount_mount: mount(generic): calling mkdir_path /nas/home/theUser mount(generic): calling mount -t cifs -o domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 //nas.example.com/theUser /nas/home/theUser >> mount error(126): Required key not available >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) mount(generic): failed to mount //nas.example.com/theUser (type cifs) on /nas/home/theUser dev_ioctl_send_fail: token = 727 failed to mount /nas/home/theUser journalctl ============== kernel: CIFS: fs/cifs/cifsfs.c: Devname: //nas.example.com/theUser flags: 0 kernel: CIFS: fs/cifs/connect.c: Domain name set kernel: CIFS: fs/cifs/connect.c: Username: theUser kernel: CIFS: fs/cifs/connect.c: file mode: 0755 dir mode: 0755 kernel: CIFS: fs/cifs/connect.c: VFS: in mount_get_conns as Xid: 684 with uid: 0 kernel: CIFS: fs/cifs/connect.c: UNC: \\nas.example.com\theUser kernel: CIFS: fs/cifs/connect.c: Socket created kernel: CIFS: fs/cifs/connect.c: sndbuf 16384 rcvbuf 131072 rcvtimeo 0x834 kernel: CIFS: fs/cifs/connect.c: Demultiplex PID: 532823 kernel: CIFS: fs/cifs/fscache.c: cifs_fscache_get_client_cookie: (0x000[...]8/0x0000[...]d) kernel: CIFS: fs/cifs/connect.c: VFS: in cifs_get_smb_ses as Xid: 685 with uid: 0 kernel: CIFS: fs/cifs/connect.c: Existing smb sess not found kernel: CIFS: fs/cifs/smb2pdu.c: Negotiate protocol kernel: CIFS: fs/cifs/transport.c: Sending smb: smb_len=106 kernel: CIFS: fs/cifs/connect.c: RFC1002 header 0xfa kernel: CIFS: fs/cifs/smb2misc.c: SMB2 data length 122 offset 128 kernel: CIFS: fs/cifs/smb2misc.c: SMB2 len 250 kernel: CIFS: fs/cifs/transport.c: cifs_sync_mid_result: cmd=0 mid=0 state=4 kernel: CIFS: fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release kernel: CIFS: fs/cifs/smb2pdu.c: mode 0x1 kernel: CIFS: fs/cifs/smb2pdu.c: negotiated smb3.0 dialect kernel: CIFS: fs/cifs/asn1.c: OID len = 7 oid = 0x1 0x2 0x348 0xbb92 kernel: CIFS: fs/cifs/asn1.c: OID len = 7 oid = 0x1 0x2 0x348 0x1bb92 kernel: CIFS: fs/cifs/asn1.c: OID len = 10 oid = 0x1 0x3 0x6 0x1 kernel: CIFS: fs/cifs/connect.c: Security Mode: 0x1 Capabilities: 0x300057 TimeAdjust: 0 kernel: CIFS: fs/cifs/smb2pdu.c: Session Setup kernel: CIFS: fs/cifs/smb2pdu.c: sess setup type 5 kernel: CIFS: fs/cifs/cifs_spnego.c: key description = ver=0x2;host=nas.example.com;ip4=10.0.0.1;sec=krb5;uid=0x0;creduid=0x12D687;user=theUser;pid=0x82155 cifs.upcall[532824]: key description: cifs.spnego;0;0;39010000;ver=0x2;host=nas.example.com;ip4=10.0.0.1;sec=krb5;uid=0x0;creduid=0x12D687;user=theUser;pid=0x82155 cifs.upcall[532824]: ver=2 cifs.upcall[532824]: host=nas.example.com cifs.upcall[532824]: ip=10.0.0.1 cifs.upcall[532824]: sec=1 cifs.upcall[532824]: uid=0 cifs.upcall[532824]: creduid=1234567 cifs.upcall[532824]: user=theUser cifs.upcall[532824]: pid=532821 cifs.upcall[532824]: get_cachename_from_process_env: pathname=/proc/532821/environ cifs.upcall[532824]: drop_all_capabilities: Unable to apply capability set: Success cifs.upcall[532824]: Exit status 1 kernel: CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed kernel: CIFS: VFS: \\nas.example.com Send error in SessSetup = -126 kernel: CIFS: fs/cifs/connect.c: VFS: leaving cifs_get_smb_ses (xid = 685) rc = -126 kernel: CIFS: fs/cifs/dfs_cache.c: __dfs_cache_find: search path: \nas.example.com\theUser kernel: CIFS: fs/cifs/dfs_cache.c: get_dfs_referral: get an DFS referral for \nas.example.com\theUser kernel: CIFS: fs/cifs/fscache.c: cifs_fscache_release_client_cookie: (0x0000[...]8/0x00000[...]d) kernel: CIFS: fs/cifs/connect.c: VFS: leaving mount_put_conns (xid = 684) rc = 0 kernel: CIFS: VFS: cifs_mount failed w/return code = -126

2 2

[arch-general] [aur] Could anybody help with Meshroom installation?
by Peter Nabbefeld 13 Dec '20

13 Dec '20

Hello, I tried to install alice-vision-git together with meshroom, but it seems sth. isn't found: Meshroom-2020.1.1]$ Meshroom WARNING:root:== The following "submitters" plugins could not be loaded == * simpleFarmSubmitter: No module named 'simpleFarm' Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/cx_Freeze/initscripts/__startup__.py", line 40, in run module.run() File "/home/peter/.cache/pacaur/meshroom/src/meshroom/setupInitScriptUnix.py", line 39, in run File "meshroom/ui/__main__.py", line 10, in <module> File "/home/peter/.cache/pacaur/meshroom/src/meshroom/meshroom/ui/app.py", line 18, in <module> File "shibokensupport/__feature__.py", line 142, in _import File "/home/peter/.cache/pacaur/meshroom/src/meshroom/meshroom/ui/reconstruction.py", line 169, in <module> File "/home/peter/.cache/pacaur/meshroom/src/meshroom/meshroom/ui/reconstruction.py", line 253, in ViewpointWrapper TypeError: A constant property cannot have a WRITE method or a NOTIFY signal. The strange point for me here is that Meshroom tries to find sth. using my cache - I don't think that's the way Meshroom (or any other application) should work ... Kind regards Peter

1 0

[arch-general] ArchLinux Installation with full encryption and uefi but without lvm
by joerg.jellissen＠t-online.de 13 Dec '20

13 Dec '20

Hello, i have one question. Is it possible to install ArchLinux on an UEFI System with full encryption BUT without lvm? I found no tutorial to do this. I also like to do this without grub. But i don’t understand the differences between systemd / systemd-boot and bootctl. ☹ My english is good, but not so good. ☹ I am sorry for this. Thanks for helping me Mit freundlichen Grüßen Jörg Jellissen Friesenstraße 3 47445 Moers M: 0157 35344218 http://www.joerg-jellissen.de joerg.jellissen(a)t-online.de <mailto:joerg.jellissen@t-online.de>

2 1

[arch-general] pacman trust DB issue
by Frank 13 Dec '20

13 Dec '20

Good afternoon, I'm having an issue with pacman. When running pacman to e.g. do an upgrade I get the following error message: error: cifs-utils: signature from "Tobias Powalowski <tobias.powalowski(a)googlemail.com>" is unknown trust :: File /var/cache/pacman/pkg/cifs-utils-6.11-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] I checked system time which should be fine, so I did a pacman-key --init pacman-key --populate archlinux this ends with the following error: ==> ERROR: Trust database could not be updated. What is it I'm missing? THX Frank -- Frank Zimmermann Jami: rhoihesse Matrix: @zimbi:matrix.org

2 2

[arch-general] PA over JACK: excessive work?
by riveravaldez 11 Dec '20

11 Dec '20

Hi, I'm using PulseAudio over JACK and noticed in htop that while not doing nothing PA works much more than when idle alone, is this normal/right? This is what I do: Close everything that uses audio. Start JACK through qjackctl. $ pulseaudio --kill $ pulseaudio --start (So, PA now works as some kind of bridge redirecting audio through JACK.) $ pactl load-module module-jack-sink $ pactl load-module module-jack-source (So I have general sink/source ports to make connections.) But then I check htop and PA is working all the time. Is this normal? Am I doing something wrong? Thanks a lot in advance.

2 1

[arch-general] FreeCAD and KiCAD depend on different opencascade versions
by Ricardo Band 11 Dec '20

11 Dec '20

Ohai, I'd like to use FreeCAD and KiCAD on the same system but I can't install them both from the official repos because kicad depends on opencascade und freecad depends on opencascade74. I can't install both because these two opencascades don't like to be installed together. Is their a solution in sight? Can we recompile freecad against the newer opencascade? At the moment I'm using the AppImage version of freecad and the repo version of kicad. -- Greetings Ricardo Band https:// www.ricardo.band mailto:// email(a)ricardo.band xmpp://jabber@ricardo.band

2 1

[arch-general] CPU spikes when lid closed
by David Rosenstrauch 04 Dec '20

04 Dec '20

I've been having an odd problem. My laptop works like a charm on its own. However, when it's connected to a USB-C dock and screen, suddenly apps that were working great start eating up lots of CPU. (Such as Firefox, Thunderbird, and Zoom.) After a bit of debugging, I realized that the issue isn't even whether I'm connected to the dock, but rather whether the laptop lid is open or closed: close the lid and all those apps eat up CPU; open the lid and CPU drops and everything is groovy. I can't for the life of me figure out what's causing this, and my searching hasn't been able to turn up a clear cause or solution. Would anyone happen to have experienced the same issue, or be able to point me in the right direction as to the cause? I'm running XFCE, with the display settings set to "mirror displays" (i.e., the internal laptop screen and the external HDMI monitor). Thanks, DR

2 2

[arch-general] Softphone
by Jörg Jellissen 03 Dec '20

03 Dec '20

Hello, i am currently searching for another software solution for a SIP Softphone on Gnome in ArchLinux. I didn't found a good solution. In AUR there is linphone available but i think this is terrible for me. Thanks for help Regards

3 2

[arch-general] General protections faults / kernel panics with the Apple Magic Trackpad 2
by Merlin Büge 02 Dec '20

02 Dec '20

Hi all. I think I need some help with debugging an issue I have. I recently bought an "Apple Magic Trackpad 2" for reducing strain on my hand (since I have some RSI[0] issues currently), which is supported in Linux since version 4.20[1]. After connecting it to my laptop it worked instantly at first, but "sometimes" un- and replugging the trackpad crashes my system. Often it works fine, but every now and then it triggers `general protection faults` (often while opening big applications like Firefox), causes my status bar to hang up, and usually ends in a freeze. Sometimes, just before the freeze I get thrown back to the console and see a kernel panic at the end of the log. The laptop is a Thinkpad X200 running stock BIOS, Arch Linux and sway, with microcode updates enabled. I could also reproduce the issue with Gnome on Wayland. On Xfce I could not reproduce the issue, and also not on Fedora (which I installed on the same laptop to the same SSD, for testing). I'm using the trackpad only via the USB cable, not via bluetooth. Attached is a snippet from the dmesg output with debug logging enabled (appended `debug` on the kernel cmdline) showing some of the protection faults. I uploaded the full dmesg output here [2]. In this specific dmesg output, most of the protection faults happened concurrently while I was opening Firefox (several times to provoke the crash). A photo of the kernel panic can be found here [3]. This kernel bug report[4] and related arch report[5] seem related to the issue, maybe it's even the same issue? However, the kernel bug report mentions that the issue only affects linux >=5.8.7. In my case, I could reproduce the issue with the following linux versions (installed from the Arch Linux archive): 4.20.0 4.20.1 4.20.3 4.20.7 5.0.0 5.0.13 5.4.74 5.2.0 5.8.6 5.8.7 5.8.8 5.9.2, 5.9.4 5.10rc-2 The USB ID of the trackpad is 05ac:0265. Because I'm very inexperienced with kernel debugging I would appreciate any help/pointers to what would be wise to test next. If this is likely to be an issue with the Linux kernel and not arch-related (unsure, since I could not reproduce it on other distros), please tell me so and I will post to the kernel bug tracker instead. Thanks! Merlin Büge [0]: https://web.eecs.umich.edu/~cscott/rsi.html [1]: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/commit/?h=for… [2]: https://0x0.st/idkH.json [3]: https://0x0.st/idkz.jpg [4]: https://bugzilla.kernel.org/show_bug.cgi?id=209239 [5]: https://bugs.archlinux.org/task/67860 -- Merlin Büge

1 1