| Summary: | Touchpad settings module sometimes does not apply settings | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Al Williams <alw> |
| Component: | kcm_touchpad | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | cfeck, groszdanielpub, nate |
| Priority: | NOR | ||
| Version: | 5.17.5 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Al Williams
2014-04-27 21:03:25 UTC
Could you try "touchpad" package from kubuntu experimental ppa? Yes I can. I am not certain what triggers the current set to forget the saved settings. Not sure if it is relogin or perhaps not JUST relogin so it isn't always reproducible. but eventually it does forget. I will try the kubuntu experimental version. Actually, perhaps I'm confused. The PPA has touchpad in it (according to https://launchpad.net/~kubuntu-ppa/+archive/experimental), but the package I have installed is kde-touchpad. If I apt-get update and then try to install kde-touchpad it says I am up to date. If I try to install touchpad it says it can't find it. Exactly what do you want me to try? Of course, I meant kde-touchpad. I don't use KUbuntu so I don't know how packages are exactly named and can't give any advice on how to upgrade. Package in PPA has been updated yesterday. I managed to download the dpkg, uninstalled the Kubuntu package and installed this one. So far so good. Unfortunately, even with the new package the problem persists. I can't tell exactly what triggers it to not reload the settings. It knows the settings do not match as it does show a warning that the current settings don't match the saved settings. This problem may be caused by X thinking that touchpad is plugged in (for example, "udevadm trigger"). I am working on fix for it. I have a similar problem with a keyboard. I have a custom piece of software that enables its "special keys" and sometimes it "forgets" so it makes sense that the USB bus is perhaps disconnecting/reconnecting and things aren't getting reloaded. Not sure why that should be true, but it would explain both issues. Could you attach your dmesg and Xorg.0.log here? (when touchpad/keyboard settings are reset) Now latest kcm-touchpad from git master re-applies settings after "udevadm trigger". Package in Kubuntu Experimental PPA should update soon. Please, let me know if it works for you now. Circular scrolling is always enabled on startup even though I disabled it. If I open the kcm, it correctly recognizes that it's not what I saved, and if I click Apply, it disables circular scrolling. Other settings are generally remembered. (I think other settings were forgotten once or twice too, but I'm not sure.) It is on openSUSE 13.1 from the KDE Current Extra repository. The latest kcm-touchpad in Experimental PPA (20140513+r312~2746b19+2) didn't fix my issue. I can't figure out what the trigger is but just sometimes it randomly forgets the preset settings in the actual hardware. When it will forget settings next time, could you save dmesg and Xorg.0.log and attach them here? On my machine, the touchpad settings occasionally (like once in a week) change to some (default?) settings, on an already running system. I wrote a script to monitor the synclient output and it just changed for no apparent reason. I don't know whether this issue is related to the fact that some settings are not applied at startup, and/or to the issue reported by Al Williams. I don't have anything recent in the Xorg log. I have the following lines in dmesg: [14045.649047] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [14045.664671] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced. But there are such lines from earlier too, when nothing happened to the touchpad settings, so I doubt that they are related. Hello! This bug report concerns the Synaptics version of the Touchpad page, which is no longer supported in Plasma 6. Can you please see if the issue still happens when using Libinput? If so, please change the status back to "REPORTED." If not, go ahead and change it to "RESOLVED FIXED", or let the bot do it automatically after a month. Thanks! 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! |