I can confirm, the touchscreen is not responsive after it goes to sleep, even without using the stylus. I have to restart the machine to get the functionality back.
I want to believe that the touchscreen control turns off to conserve battery, but something either in the firmware or the systemd doesn’t turn it back on properly when waking up.
Gnome 49 on Arch, similar issues. The stylus also degrades in quality over time after each reboot. Starts working nearly perfectly when I reboot my computer, and slowly starts getting more buggy over time. I think this has something to do with the touchscreen though, as the touchscreen also usually stops working in a similar way, along with the pen.
I have the same issue on Fedora 43 with GNOME 49 (Linux 6.17.11-300.fc43.x86_64)
Interestingly, using libinput , I can see that touch events are still recorded: libinput record /dev/input/event8 shows all events when using the touchscreen. So there must be something that prevents those events being routed to the shell.
This seems similar to my issue, though I don’t think the computer went to sleep. I was working in an art program through Bottles, so was using the stylus. After a while, I went to select something on my taskbar with my finger, but no reaction. Thought it might be a tablet mode issue, but it persists after flipping back to normal laptop mode. Stylus and touchpad work normally.
Essentially same specs as the original post, but I use KDE. Has anyone sent a bug report to the Fedora team yet?
I use my new Framework Laptop 12 for two weeks and I found similar problem.
In my case the touchscreen sometimes stops working after returning from tablet mode to standard. I need to log out and log in to make this work again. But also, that’s even more frustrating, when touchscreen stops working, I also cannot get laptop to suspend. When clicking power button (which is assigned to sleep action) I get pop up that PC will be shutdown in a minute (not suspend, just shutdown).
I experienced a similar problem on Ubuntu today, stylus and touchpad was working fine, regular touch was not working in tablet mode nor laptop mode but my laptop hadn’t suspended at all since last using touch. I attempted a sudo modprobe -r hid_multitouch (I’m not sure if this module services / governs the touchscreen device though) just to try something out, and for some reason the touch came back before I even reloaded the driver? I’m not able to reproduce the touch going out again so I can’t test my “fix” until it happens again. I’ve re-enabled hid_multitouch and touchscreen is still working fine. I don’t actually believe what I did fixed anything, my touch just coincidentally started functioning again?
Touchscreen stopped working after stylus use, general glitchiness and a suspend, so I tried the sudo modprobe -r hid_multitouch again and the touchscreen started working again. Seems like it might be a potential fix? Touchscreen works regardless of whether hid_multitouch is reenabled, but since its enabled on boot, I reenable it immediately after disabling.
Are you re-enabling the module? You do so without the -r argument, like so: modprobe hid_multitouch. In one line: sudo modprobe -r hid_multitouch && sudo modprobe hid_multitouch. I made a .desktop file pointing to a bash script containing this, and now can launch it to fix the touchscreen easily.
I did do modprobe -r hid_multitouch instead of modprobe hid_multitouch! I see, I’ll make sure to do the right one next time. Weird that it enabled my touchscreen and disabled my trackpad though.
Sorry, I wasn’t clear. You should run both commands. Modprobe allows you to load or remove modules from the kernel that allow the OS to interface with hardware. When we remove the multitouch module, we are removing the touch devices (touchscreen, and potentially trackpad). Then we reload this module. sudo modprobe -r hid_multitouch REMOVES the multitouch human input device, then sudo modprobe hid_multitouch loads it in again. You can use a double ampersand && to run a second command right after the first, allowing you to do both commands in one line.
Then for simplicity, you can create a .desktop file pointing to an executable bash script that just contains: