Description of problem: Synaptiks disables touchpad when USB mouse is connected only after the system is completely loaded (after user login). If the mouse is connected prior to booting the system, both the mouse and the touchpad are active. Unplugging and plugging back the mouse disables touchpad. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Install synaptiks. 2. Go to KDE System Settings - Touchpad Settings and Management (for synaptiks, not the one for KDE) and check "Automatically switch off touchpad if a mouse is plugged". Apply. 3. Plug in the mouse - touchpad is disabled. 4. Power off the laptop (or restart) with mouse plugged. 5. After logging in both mouse and touchpad are active. 6. Unplug and plug the mouse back - touchpad is inactive again.
cc'ing committers of synaptiks
CC: (none) => balcaen.john, fundawang, marja11
I guess it is not the responsibility of synaptiks when during boot up, maybe udev?
(In reply to comment #2) > I guess it is not the responsibility of synaptiks when during boot up, maybe > udev? cc'ing some udev committers
CC: (none) => dmorganec, mageia, thierry.vignaudSource RPM: synaptiks-0.4.0-3.mga1 x86_64 => synaptiks-0.4.0-3.mga1 x86_64 udev
I can't see this bug being fixed in MGA1, but MGA2 has a newer synaptiks version. There are no udev rules in the synaptiks package so I cannot see this being udev's responsibility in any way. To avoid doubt, I believe this is a purely localized problem in synaptiks. It is responsible for detecting these other device and disabling the touch pad. As this is a user preference, it will not affect e.g. KDM when logging in. It will only affect the users' desktop after logging in. My guess is that synaptiks is listening in some capacity for plug/unplug events and acting on those, but not properly scanning on startup. I say this without any specialist knowledge of synaptiks code or operation, just going on a general "how things work" principle, and thus I *could* be wrong here. If it's still a problem I would suggest an upstream bug report as we do not customize this package (we did in MGA1, but I cannot see that patch being problematic). My $0.02.
CC: mageia => (none)
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Version: 1 => 2
CC: (none) => stormiSource RPM: synaptiks-0.4.0-3.mga1 x86_64 udev => synaptiks-0.4.0-3.mga1
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD