https://bugs.kde.org/show_bug.cgi?id=396335
Pedro V <voidpointertonull+bugskde...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
CC| |voidpointertonull+bugskdeor
| |g...@gmail.com
Status|REPORTED |NEEDSINFO
--- Comment #1 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
