SUMMARY Mouse and keyboard does not work after logging in STEPS TO REPRODUCE 1. log in OBSERVED RESULT No mouse pointer on the screen, no keypresses being acted upon, lights on both devices up/getting power. No journal messages about plasma input whatsoever. Kernel sees mouse and keyboard being connected and never disconnected/dropped. EXPECTED RESULT Working mouse and keyboard SOFTWARE/OS VERSIONS Linux: 6.11.6-arch1-1 (64-bit) KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION Wayland
This is highly unlikely to be a KDE issue. I would recommend following up on the Arch forum first. If troubleshooting done there indicates that it may be a KDE issue of some kind, we can re-open this. Good luck!
I am quiet certain it is specifically KDE related since such issue is not present in any other DE (tested i3, xfce, GNOME). Also my loading screen process terminates with exit code 15 if I don't move my mouse around after I complete the login, I am not even sure where to begin digging on this issue, I request help here because that's what is not working, everything besides kwin and ksplash. This issue is present for over 3 months, I am trying to migrate to KDE monthly and so far this is the only issue left that is not going away as updates go by. I can provide journal but I am not sure what exactly should I look for in there, besides following there is nothing relevant. ``` 09:59:19 tower0 systemd[1179]: plasma-ksplash.service: Failed with result 'timeout'. 09:59:19 tower0 systemd[1179]: plasma-ksplash.service: Main process exited, code=killed, status=15/TERM 09:59:19 tower0 systemd[1179]: plasma-ksplash.service: start operation timed out. Terminating. 09:58:40 tower0 kded6[1401]: kf.dbusaddons: The kded module name "kded_plasma-welcome" is invalid! 09:58:40 tower0 kded6[1401]: QDBusObjectPath: invalid path "/modules/kded_plasma-welcome" ```
Thing is, this is a bug tracker, not a troubleshooting service. It sounds like a whole host of stuff on your system is in a bad state up right now. If and when any of those issues get pinpointed to being bugs in our code, we can track them on this bug tracker. Until then, please take the troubleshooting process somewhere else. Thanks!