Sks
July 17, 2026, 7:33am
1
Hello everyone, I just installed 4.3 on my new laptop an IdeaPad. When I open an appvm the mouse lags a little, not much but annoyingly much. This is systemwide so if I open an appvm and I go to qubes manager to do something it will lag sometimes. Could it be the kernel? Thanks
Atrate
July 17, 2026, 9:33am
2
I’ve also experienced this on several laptops, including certified hardware. I am not sure there’s a solution right now.
opened 08:08AM - 26 Nov 19 UTC
C: Xen
P: default
hardware support
needs diagnosis
waiting for upstream
affects-4.1
affects-4.2
eol-4.2-candidate
**Qubes OS version**
Qubes R4.0.2-rc2
**Affected component(s) or functionali… ty**
Elan 1200 Touchpad
**Brief summary**
The touchpad doesn't work properly.
**To Reproduce**
1. Use a laptop with ELAN1200 touchpad (I'm using Zenbook UX410UA)
2. Install Qubes R4.0.2-rc2 on it, optionally update dom0
3. Try to use the touchpad to move the cursor
**Expected behavior**
The touchpad should work without any errors or erratic behavior.
**Actual behavior**
The touchpad initially works for a few seconds then it gradually breaks down completely. Mouse pointer doesn't move smoothly, phantom clicks are created, and the syslog gets spammed with errors.
**Screenshots**
N/A
**Additional context**
Okay, so my laptop won't let me touch its naughty place. Each time I try to use the touchpad it will initially work for a few seconds, but then the behavior will quickly worsen with continued use until it becomes completely unusable (I'm talking about like 10 seconds or so after first use). The symptoms include jumping cursor (dropped frames), phantom left button clicks, random scrolls, click & drag events as the text gets selected, etc. All this happens when using a single finger to move the cursor without pressing any buttons or using the mouse.
When happening, the syslog will get spammed with messages like these:
```
[ 317.989978] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 317.990656] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 318.046554] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 318.047136] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 318.102763] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 318.103339] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 318.168683] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/82)
[ 319.705539] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/82)
[ 319.762092] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/82)
[ 320.050799] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 320.107179] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
[ 320.107769] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466)
```
Notice that there are two types of errors. The 16/82 lines only rarely happen when I am touching the touchpad with a single finger and moving it around a bit. But as soon as I remove my finger, the 16/16466 lines will be printed out with very high frequency until I put my finger back or until some time later after a very large number of them are printed out - I'm assuming this is when the touchpad goes to sleep due to inactivity. I've done some searching and it seems like these bugs should already be patched some recent kernels. As usual, I've tested the hardware in Debian Buster 10 Live LXQt and Ubuntu Mate 19.10 Live, and the touchpad appears to work fine in both cases. Doing a "rmmod i2c-hid" stops the syslog errors, but also disables the touchpad.
Some more info:
```
[root@dom0 ~]# dmesg | grep ELAN
[ 17.507865] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[ 17.507875] i2c_hid i2c-ELAN1200:00: Linked as a consumer to regulator.0
[ 17.507876] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator
[ 17.539311] input: ELAN1200:00 04F3:3044 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-6/i2c-ELAN1200:00/0018:04F3:3044.0001/input/input7
[ 17.539365] input: ELAN1200:00 04F3:3044 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-6/i2c-ELAN1200:00/0018:04F3:3044.0001/input/input8
[ 17.539412] hid-generic 0018:04F3:3044.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3044] on i2c-ELAN1200:00
[ 17.742568] input: ELAN1200:00 04F3:3044 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-6/i2c-ELAN1200:00/0018:04F3:3044.0001/input/input18
[ 17.742703] hid-multitouch 0018:04F3:3044.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3044] on i2c-ELAN1200:00
```
Output for dmesg is almost identical in debian/ubuntu live so I won't post those.
```
[root@dom0 ~]# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
```
```
[root@dom0 ~]# libinput-list-devices
...
Device: ELAN1200:00 04F3:3044 Touchpad
Kernel: /dev/input/event8
Group: 6
Seat: seat0, default
Size: 103.23x70.90mm
Capabilities: pointer
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock: disabled
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: *two-finger edge
Click methods: *button-areas clickfinger
Disable-w-typing: enabled
Accel profiles: none
Rotation: n/a
...
```
**Solutions you've tried**
1. Upgraded the kernel (4.19.82-1.pvops.qubes.x86_64) to kernel-latest (5.3.7-1.pvops.qubes.x86_64 or 5.3.9-1.qubes.x86_64) in dom0 - no dice
**Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted**
https://www.qubes-os.org/doc/newer-hardware-troubleshooting/
**Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues**
none
opened 09:50AM - 18 Jan 26 UTC
C: Xen
P: major
hardware support
needs diagnosis
affects-4.3
certified hardware
### Qubes OS release
Qubes OS 4.3
### Brief summary
Random mouse/keyboard freez… es (1-5 seconds) on Qubes-certified NovaCustom V560TU (Meteor Lake). Caused by Xen reporting spurious thermal throttling while actual CPU temperatures are normal (45-61°C under full load, well below 110°C threshold).
### Steps to reproduce
1. Use the system normally on a NovaCustom V560TU with Meteor Lake CPU
2. Wait — freezes occur randomly, not correlated with load or specific actions
3. Run `xl dmesg | grep -i temperature` to see thermal throttling messages
### Expected behavior
- No input freezes during normal operation
- Thermal throttling should only occur when CPU temperature actually approaches threshold (110°C)
### Actual behavior
- Mouse and keyboard freeze randomly for 1-5 seconds
- `xl dmesg` shows multiple CPUs reporting thermal throttling:
```
(XEN) CPU0: Temperature above threshold
(XEN) CPU0: Running in modulated clock mode
(XEN) CPU2: Temperature above threshold
(XEN) CPU4: Temperature above threshold
(XEN) CPU6: Temperature above threshold
(XEN) CPU8: Temperature above threshold
(XEN) CPU9: Temperature above threshold
(XEN) CPU10: Temperature above threshold
(XEN) CPU11: Temperature above threshold
(XEN) CPU16: Temperature above threshold
(XEN) CPU18: Temperature above threshold
```
- `sudo modprobe coretemp` fails: "could not insert coretemp: No such device"
- Hardware sensors (`sensors`) show normal temperatures (RAM 47-48°C, NVMe 31-44°C)
### Additional information
**This is Qubes-certified hardware.**
**Verified on Linux Mint (same hardware, no Xen):**
- `coretemp` module loads correctly and reports all CPU core temperatures
- Stress test (`stress-ng --cpu $(nproc) --timeout 60s`): max temperature reached **61°C**
- All temperatures well within safe range
**Conclusion:** Xen misinterprets Meteor Lake thermal sensor data. The hardware and thermal paste are working correctly — this is a Xen/Meteor Lake compatibility issue.
**Related:**
- Ubuntu thermald bug #2028217 (Meteor Lake support issues)
- `coretemp` kernel module lacks Meteor Lake support
**System info:**
- Hardware: NovaCustom V560TU (Qubes-certified)
- CPU: Intel Core Ultra (Meteor Lake)
- BIOS: Dasharo (coreboot+UEFI)
Does this happen even if there are no USB connections functioning? I have this problem when i’m copying files to external hard disk or using usb web camera or usb mic.
I am using QubesOS 4.2.4 on @novacustom V56. This has been an issue that I experienced for a long time, but today I got really annoyed that I finally report it here.
I plug in a USB drive (simple stick) to my USB port (the usual usb type-a or type-c, in both cases this annoyance is present). I click on the USB icon on the xfce4 tray, find my USB drive, and attach it to one of my regular debian/whonix qubes. In the qube, I fill one of the partitions in the USB stick with inputs from /dev/rand…
opened 03:06PM - 07 Mar 21 UTC
closed 02:27PM - 07 Dec 24 UTC
C: other
P: default
hardware support
affects-4.1
eol-4.1
**Qubes OS version**
R4.04
**Affected component(s) or functionality**
…
USB mouse movement
**Brief summary**
The mouse starts stuttering if there is some network traffic.
Was not visible at 4.02.
**How Reproducible**
Happens all the time
**To Reproduce**
Steps to reproduce the behavior:
1. Fresh install
2. update template
3. during the template has network access the mouse stutters.
**Expected behavior**
smooth movement
**Actual behavior**
**Screenshots**
**Additional context**
**Solutions you've tried**
Increase memory of sys-net.
**Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted**
**Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues**
unman
July 17, 2026, 1:53pm
4
For another point, I have not experienced this on any of the Thinkpads
or certified derivatives.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
Sks
July 17, 2026, 2:07pm
5
What about an external mouse? Is it also the same?
Sks
July 18, 2026, 6:25am
6
No this just happens when I open a load(appvm) no USB passthroughs or USB connected if that’s what you mean
Atrate
July 20, 2026, 5:25pm
7
Mostly no. Even under high load external mouse lag happens extremely rarely for me, it’s a way better experience than touchpad.
To narrow it down, I would definitely exclude it’s about kernel, memory balancing and having different values for mem and maxmem set for dom0. Disclaimer: I haven’t read GitHub topics quoted.
Sks
July 21, 2026, 9:57am
9
I don’t know how but the issue was fixed by itself. After a few restarts