| Summary: | Laptop touchpad sometimes doesn't work after login | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | indecisiveautomator |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | notmart, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.23.90 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
indecisiveautomator
2022-01-19 21:14:37 UTC
this is probably due to the kded that can disable the touchpad, weird that doesn't seem to respect the settings though Please attach any logs from journalctl --user -b Thanks! The next time I am able to reproduce this bug, I will attach the logs. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! The bug occured for me again just today after turning my laptop on for the first time in about a week. I ran the command `journalctl --user -b` and saved it to a text file using `journalctl --user -b > log.txt`. The file is quite long, about 200 lines. I could attach all of it but is there anything specific I should search for to send? To my untrained eye I can't see anything related to touchpads or anything major that fails, there are some odd complaints about latte dock stuff (I don't use latte dock) and appimagelauncherd complaining some files don't exist. Other than that the services it tries to start all start up properly as far as I can see. But again, if there's something I should look out for I can just post that, or if there are any other commands I should run just let me know. I'll keep my laptop on to help diagnose the issue 🙂 This is the longest I've kept my laptop on while the touchpad has not worked. Putting the laptop to sleep and waking it again has not worked. I am unsure if, in this specific case, that the trackpad worked on the login screen. I didn't try to move it. Also, there is no battery indicator in my system tray. I can't open it to access the battery option that's normally in there as far as I know, but this behaviour is definitely strange. I noticed some other potentially odd behaviour, though I could just be remembering incorrectly so please bear with me. Usually in System Settings > Input Devices > Touchpad, there is a dropdown box with my touchpad listed. However right now, there is no such dropdown box. The system settings screen starts with the "General" list where "Device Enabled" is checked. I am using a point release behind on my laptop, but I didn't want to update and reboot as I wanted to keep the laptop in this touchpad-less state for as long as possible. Below is some updated system information from the initial bug report: Kernel: 5.16.11-arch1-2 (64bit) Plasma version: 5.24.2 (Wayland session) KDE Frameworks: 5.91.0 Qt version: 5.15.2 I'd just like to note again that this bug is very rare, and that a reboot or two usually fixes it, but any potential of fixing it or at the very least documenting that it can occur may be beneficial 🙂 |