#1107966 general: Touchpad disabled after resume from sleep

Package:
general
Source:
general
Submitter:
Chris Maaskant
Date:
2025-07-27 20:51:02 UTC
Severity:
normal
Tags:
#1107966#5
Date:
2025-06-18 06:24:02 UTC
From:
To:
Dear Maintainer,

I have installed Debian Trixie with KDE/Plasma 6.3.5 on a HP Pavilion laptop.
After I close the lid the laptop suspends to ram succesfully.
Then when I open the lid to wake up the laptop all goes well, except that the touchpad is turned off.
Not only is it turned off, but in KDE/PLasma systemsettings the touchpad is then also disabled (the checkbox to enable the toucpad is not checked).

Since I had this problem too on Opensuse Tumbleweed with simular KDE/Plasma version and kernel version.
And this does not happen when I suspend and wake up using Icewm and not KDE/Plasma.
So I think that this is a problem with KDE/Plasma.

This problem happens on both a X11 and wayland session, and running on ac-power and on battery.
And it never did for years on multiple Linux distros including Debian Bookworm running KDE/Plasma 5.x.

So it seems like a regression in KDE/Plasma 6.x
My appologies that I can not be more specific as I really do not know what is causing this.

Thank you for your time,
Chris Maaskant.

#1107966#10
Date:
2025-06-21 20:57:45 UTC
From:
To:
control: tags -1 + moreinfo

Dear Chris,


Le 18 juin 2025 08:24:02 GMT+02:00, Chris Maaskant <gchmw@ziggo.nl> a écrit :

[…]

I'd say this must have something to do with your specific hardware. At least it's not a widespread issue for sure and it's the first time I hear about this.

That you see it now may be related to Plasma 6 but it may also come from newer kernels and Plasma triggering some issue with these.

If you could share the bits of the system logs before sleep / after wake that would probably be useful.


Happy hacking,
--
Aurélien

#1107966#17
Date:
2025-06-22 06:37:16 UTC
From:
To:
Aurélien COUDERC schreef op za 21-06-2025 om 22:57 [+0200]:

I have installed Opensuse Tumbleweed now on my laptop.
I have reported these 'problems' on discuss.kde.org since it does not
seem to be distribution specific.
But if there is a solution posted there, I will report that here also.