| Summary: | Gaming mouse loses configuration after booting windows, is restored by reconnecting it again | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | David <david.cortes.rivera> |
| Component: | kcm_mouse | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | postix, unassigned-bugs, voidpointertonull+bugskdeorg |
| Priority: | NOR | ||
| Version: | 5.13.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=415156 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
David
2018-07-09 08:16:42 UTC
I don't think this is relevant to KDE and likely that's why it didn't get attention at all. Is this still a problem to begin with? You skipped describing the behavior of booting straight into Linux, but I suspect it's the same as what happens when the mouse gets plugged in while Linux is running. If that's the case, then the problem is not even with Linux, you should encounter the same problem even by just booting into a different Windows setup without the mouse specific driver Generally it sounds like that the Windows driver leaves the hardware in a dirty state or it intentionally does some kind of reset when exiting which is surprisingly common mostly with "gaming" devices and lighting control. In that case there are the following possible cases: - Most desirably the faulty Windows driver logic would get fixed because that's the source of the problem after all - If there's a hardware specific driver in Linux for the device, then a workaround can be added there, although it likely won't be desired if the problem is really caused by just software The reproducer description is likely insufficient though. I happen to have a Logitech "gaming" mouse, and taking advantage of it storing configuration on the hardware, I made sure to only use the manufacturer bloatware in a Windows VM but not anywhere else, and although I mostly used virtualization instead of dual booting, I haven't experienced the described issue, so I suspect it doesn't happen when there's no manufacturer software running anywhere and the mouse is just merely treated as a USB HID device. 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! |