Bug 390057

Summary: Mouse does not get enabled when bluetooth is turned off
Product: [Applications] systemsettings Reporter: Jarl Gjessing <jarlgjessing>
Component: kcm_mouseAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: kde, subdiff, unassigned-bugs-null
Priority: NOR    
Version First Reported In: 5.12.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jarl Gjessing 2018-02-08 07:22:53 UTC 
Hi
This is a big problem for me since I use the computer for work, and often leave my desk without the mouse, for meetings etc.
I have checked the "disable touchpad..." because the touchpad is annoying when typing :-)
Works fine, but what I would believe is that the touchpad would get enabled again when I turn off the mouse or turn off bluetooth, but it does not. So in this case I have no pointing device at all :-(

I have to logout/in to have the mouse work again (if bluetooth were turned off) or turn on the mouse again.
Comment 1 Kai Uwe Broulik 2018-02-08 08:06:55 UTC 
I suppose the touchpad module doesn't detect/listen for this change. Does it help when you restart "kded5"? @Roman: Any idea? :)
Comment 2 Jarl Gjessing 2018-02-08 10:40:32 UTC 
Just tried to turn off the mouse and executing kded5 restart

No luck :-(
Comment 3 Kai Uwe Broulik 2018-02-08 11:47:59 UTC 
Can you check in xinput list whether the mouse still shows up afterwards? If so, this is more likely a driver, X or kernel bug.
Comment 4 Jarl Gjessing 2018-02-08 12:11:41 UTC 
Not much difference :-(
BTW, it is a logitech MX Anywhere 2 on a Lenovo T560
Before turning off mouse:
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                     id=12   [slave  pointer  (2)]
⎜   ↳ MX Anywhere 2                             id=14   [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C           id=9    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=10   [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=13   [slave  keyboard (3)]


After turning off:
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                     id=12   [slave  pointer  (2)]
⎜   ↳ MX Anywhere 2                             id=14   [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C           id=9    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=10   [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=13   [slave  keyboard (3)]
Comment 5 Roman Gilg 2018-02-08 12:46:33 UTC 
The MX Anywhere 2 entry is still there after turning the mouse / bt off. That's not an issue with the mouse kcm then, but with the underlying bt hardware detection I would say.
Comment 6 Jarl Gjessing 2020-10-10 06:50:35 UTC 
I do not see this happening anymore