After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 748525 - If mouse is plugged in, remember if touchpad should be enabled or not
If mouse is plugged in, remember if touchpad should be enabled or not
Status: RESOLVED DUPLICATE of bug 743198
Product: gnome-control-center
Classification: Core
Component: Mouse
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Ondrej Holy
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-04-27 13:39 UTC by hey
Modified: 2015-04-28 07:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description hey 2015-04-27 13:39:51 UTC
Sometimes I plug in an external mouse into my laptop. Most of the times I want the touchpad to be disabled then. But each time I plug the mouse in, I have to manually go to the settings and disable the touchpad. The setting is not remembered.

This is similar but different from issue https://bugzilla.gnome.org/show_bug.cgi?id=743198 in that the last used setting should be remembered and there’s no additional interface needed.
Comment 1 Ondrej Holy 2015-04-28 07:25:01 UTC
Thanks for your bug report. However we can't just change touchpad settings when mouse is connected without information in gui. If I understand it correctly you want set disabled-on-external-mouse if mouse is disconnected and touchpad is disabled, otherwise just enabled. However this will be confusing for users and still you have to go in settings to change the remembered state if it is wrong. So marking as duplicate of Bug 743198, because you want to have the touchpad enabled all the time regardless of the mouse, or disabled with external mouse. So you have to change setting in mouse panel also if the current setting is wrong. So Bug 743198 has same effect, but it is less confusing...

*** This bug has been marked as a duplicate of bug 743198 ***