[systemsettings] [Bug 396335] New: Gaming mouse loses configuration after booting windows, is restored by reconnecting it again

David bugzilla_noreply at kde.org
Mon Jul 9 09:16:42 BST 2018


https://bugs.kde.org/show_bug.cgi?id=396335

            Bug ID: 396335
           Summary: Gaming mouse loses configuration after booting
                    windows, is restored by reconnecting it again
           Product: systemsettings
           Version: 5.13.2
          Platform: Debian unstable
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: kcm_mouse
          Assignee: unassigned-bugs at kde.org
          Reporter: david.cortes.rivera at gmail.com
                CC: unassigned-bugs at kde.org
  Target Milestone: ---

I have a gaming mouse from Logitech of the kind that internally stores
configuration of buttons, sensitivity, and others. Whenever I boot Windows on
the computer and then reboot back to Linux, the settings seem to default to
some undesired configuration, but after unplugging the mouse cable and plugging
it again they return to their normal settings.

Steps to reproduce:
-Configure some logitech gaming mouse in a laptop on Windows OS to have custom
settings for e.g. speed or actions of extra buttons.
-Reboot the computer back to Linux. Unplug the mouse and plug it again if the
settings set in Windows didn't have an effect.
-Reboot the computer into Windows OS. Don't change any settings.
-Reboot the computer back to Linux, without unplugging the mouse.

Expected behavior:
-Mouse should have the same settings it had before rebooting into windows (the
second reboot if following the steps above).

Actual behavior:
-Mouse defaults to some other configuration. Gets back to the right
configuration if either I boot the computer with the mouse disconnected and
then plug it once the Linux system has booted, or if I disconnect it and
connect it again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.


More information about the Unassigned-bugs mailing list