See https://wayland.freedesktop.org/libinput/doc/latest/tapping.html . Upstream libinput seems to think that saving a few users from the unintended consequences of tap-to-click is worth disabling it by default for everyone. I disagree. MGA has had tap-to-click enabled since MGA1, and it is only disabled in MGA6 because we converted from the synaptics driver to libinput during the release cycle and libinput has a different default. In most cases, the default can be easily changed by adding the following entry to /etc/X11/xorg.conf.d as 10-touchpad.conf: Section "InputClass" Identifier "MyTouchpad" MatchIsTouchpad "on" Driver "libinput" Option "Tapping" "on" EndSection I believe that if tap-to-click was desirable in MGA1-5, we ought to take steps to enable it in MGA6. Affected components are (at least) the installer and the DMs, since, unlike the individual DEs, neither of these has any mechanism to allow the user to enable tap-to-click if he wants it.
(In reply to Frank Griffin from comment #0) > > In most cases, the default can be easily changed by adding the following > entry to /etc/X11/xorg.conf.d as 10-touchpad.conf: > > Section "InputClass" > Identifier "MyTouchpad" > MatchIsTouchpad "on" > Driver "libinput" > Option "Tapping" "on" > EndSection You don't say that you tested that ;-) I assume you did and that it works as desired? > > I believe that if tap-to-click was desirable in MGA1-5, we ought to take > steps to enable it in MGA6. I'm certainly not the only one for whom the "tap-to-click" feature turned into a disaster. Did _lacking_ the "tap to click" feature lead to any disaster for you? If not: Does anything indicate that a disaster could happen? CC'ing libinput packager, packaging team leaders and those of whom I've seen an opinion about tap-to-click. (A solution where it is disabled by default on all systems that have "mouse" buttons, but enabled where "mouse" buttons are missing, would have my preference)
CC: (none) => davidwhodgins, ennael1, fundawang, marja11, nic, ozkyster, rverschelde, watersnowrock
Given the various discussions that we had about this, I think the only consensual solution would be to edit the installer so that it proposes to enable or disable tab to click during the install or post-install step. Based on this option, it would write or not the above-mentioned /etc/X11/xorg.conf.d/10-touchpad.conf.
Might be worth checking if the new libinput changes things regarding this issue: tmb <tmb> 1.4.0-1.mga6: + Revision: 1042911 - 1.4.0 (improved tablet and touchpad support)
@Marja I'm fine with disable by default as long as there's a way to enable it. Yes, I did test the X11 directive; when present, tap-to-click is enabled for SDDM and disabled when it's not present. I couldn't test the installer, as I didn't know how to add it in. Oddly enough, it does NOT work for GDM, so the installer may still have a problem if this is being overridden by GTK. @Remi The link at the top of this bug report has had its version updated to 1.4.0 and still says it's disabled by default.
I have just net-installed Mga6 plasma (all defaults) on two laptops. Acer 5920 Lenovo Thinkpad T420 It was rather non-intuitive to have no taps working on the Acer during install. I can't recall whether it worked or not on the Thinkpad. After reboot the tap-to-click feature works fine on the Thinkpad, but the Acer would not work at all, despite what appeared to be correct settings in systemsettings. The Thinkpad has no /etc/X11/xorg.conf.d/*-touchpad.conf. Adding the workaround from #1 (I actually put it in xorg.conf by mistake) works fine and the Acer now responds to taps. So it seems this is hardware dependant.
CC: (none) => zen25000
When you say "it worked fine on the Thinkpad" do you mean that on reboot it worked by default or that you were able to turn it on for Plasma ? I was always able to turn it on in Plasma System Settings without using the workaround above. But that had no effect on SDDM. OpenSUSE enables tap-to-click in its installer, the DM, and GNOME by default.
(In reply to Frank Griffin from comment #6) > When you say "it worked fine on the Thinkpad" do you mean that on reboot it > worked by default or that you were able to turn it on for Plasma ? I don't know for sure - I think it was on by default but as it was not an issue I really can't remember. It was only when I could not make it work at all on the Acer that I found this bug report. > > I was always able to turn it on in Plasma System Settings without using the > workaround above. But that had no effect on SDDM. No - I can't get tap-to-click working in SDDM on either of them. > > OpenSUSE enables tap-to-click in its installer, the DM, and GNOME by default. I am currently net-installing Mga6 plasma on another Acer 7720g that I have just repaired, so I will pay close attention on this one. ;)
I have similar behavior on another lenovo. No taps during installation, or after reboot, but they work after changing systemsettings but not in sddm. While you can click with its track pad, it's about as accurate as me playing golf, so a highly frustrating experience. I feel that we should follow opensuse on this. It seems insane having a configuration that disables a key piece of hardware by default.
(In reply to Frank Griffin from comment #0) > See https://wayland.freedesktop.org/libinput/doc/latest/tapping.html . > > Upstream libinput seems to think that saving a few users from the unintended > consequences of tap-to-click is worth disabling it by default for everyone. > I disagree. MGA has had tap-to-click enabled since MGA1, and it is only > disabled in MGA6 because we converted from the synaptics driver to libinput > during the release cycle and libinput has a different default. > > > I believe that if tap-to-click was desirable in MGA1-5, we ought to take > steps to enable it in MGA6. Affected components are (at least) the > installer and the DMs, since, unlike the individual DEs, neither of these > has any mechanism to allow the user to enable tap-to-click if he wants it. (In reply to Frank Griffin from comment #6) > > OpenSUSE enables tap-to-click in its installer, the DM, and GNOME by default. (In reply to Donald from comment #8) > I have similar behavior on another lenovo. > > No taps during installation, or after reboot, but they work after changing > systemsettings but not in sddm. > > While you can click with its track pad, it's about as accurate as me playing > golf, so a highly frustrating experience. > > I feel that we should follow opensuse on this. It seems insane having a > configuration that disables a key piece of hardware by default. It is only since I've used such a touchpad that I fully understand the problem :-( Assigning to maintainer, but CC'ing some committers in case fwang is unavailable
Severity: normal => majorPriority: Normal => HighCC: (none) => jani.valimaa, thierry.vignaud, tmbAssignee: bugsquad => fundawangSummary: upstream libinput turns tap-to-click off by default => Mga 1 to 5 had tap-to-click enabled by default, but Mga6 uses libinput where it's turned off by default. There is no (easy) way to enable it in installer and in DMs
It might be good to add a note about this in the Errata, thus I'm adding the FOR_ERRATA6 keyword. Once added to https://wiki.mageia.org/en/Mageia_6_Errata please replace FOR_ERRATA6 with IN_ERRATA6.
Keywords: (none) => FOR_ERRATA6
CC: (none) => bruno
I have ever not done any disaster with tap-to-click on my HP laptop, but I miss it now, it is quite inconvenient for me now and badgering. I would prefer to have possibility to change it after an installation somewhere.
CC: (none) => greno
Still valid. Here, on a Thinkapd T60 that was installed mga5, then updated to mga6, tap to cklick is still enabled, but a fresh install on a Thinkpad T42 have no tap-to-click. Someone who know details please add to errata
CC: (none) => fri
Somehow I don't think Funda Wang is following this...
OK, can we get some resolution on this ? So far, the only dissenting voice to reverting this (Marja) seems to have recanted, and several others have voted to re-enable this. The installer has no provision for modifying the GUI as do the DEs. So this either gets enabled there or disabled. Which will it be ? SDDM (and I don't know how many other DMs) has no provision for modifying the GUI as do the DEs. So this either gets enabled there or disabled. Which will it be ? What exactly is the pushback to re-enabling this feature and from whom is it coming ? There doesn't seem to be any dissent in this bug report, but version after version of stage2 gets pushed to cauldron with no resolution and version after version of Plasma/KDE/SDDM with the same. What is the real issue here ?
Severity: major => critical
I dont see a real "push-back"... its seems more of a no-one have had time to implement it in installer/drakx tools
Meaning we could add it as defeault on in cauldron, rebuild the installer and watch the fallout...
Funda no longer maintains this package, guessing libinput counts as Base System package and re-assigning accordingly
Assignee: fundawang => basesystem
Actually I've done most of the work on libinput for the 4 past years :-) And the same for x11-driver-input-libinput which I imported. libinput is not the culprit here, that would be x11-driver-input-libinput. That said I don't think we want to alter the default behavior & behaves different ly from other distros. As for DrakX, I guess we could enables this by default during the installer. But do most users actually want that?
Source RPM: libinput => x11-driver-input-libinput
Created attachment 10064 [details] enables "Tapping" option (mga#18972) This *untested* patch would do that for DrakX installer
(In reply to Thierry Vignaud from comment #18) > That said I don't think we want to alter the default behavior & behaves > different ly from other distros. I'm no great expert on other distros, but from recent experience doing a SUSE install they have tap-to-click enabled in their installer and Windows has it enabled everywhere by default. Based on the comments here, people just expect it to work. Why would we want to break something that has worked in a consistent way through every version of MGA until someone at libinput decided they didn't like it ?
+1 People are into tapping on phones, pads etc. and just expect it to work.
Can we please re-enable tap to click everywhere, I don't understand why this would be disabled, especially with the prevalence of multitouch trackpads appearing now.
Suse does have this patch: https://build.opensuse.org/package/view_file/X11:XOrg/xf86-input-libinput/n_enable-tapping.patch?expand=1 I've no strong opinion on that front. But I would prefer this to be discussed upstream with Peter Hutterer. And I want to be sure this would not upset other laptop users.
(In reply to Thierry Vignaud from comment #23) > And I want to be sure this would not upset other laptop users. No as a laptop user, I'd like this to be the default again. Yesterday a friend unused to computers tried a Plasma laptop for the first time, and it was the first behaviour I had to change : he tried to tap like on a mobile phone.
CC: (none) => lists.jjorge
As a lazy touch typist (lazy meaning I don't keep my wrists up in the air), I'm one of the people who really dislikes having it enabled by default. If the majority of people do want it enabled, I won't complain though.
Well, it seems like overkill, but if people want a stage 1 prompt as to whether it ought to be enabled for the installer, that's OK with me. The SUSE patch, if enabled for the install and the built system, will enable tap-to-click for the entire system, including SDDM and other DMs and the DEs (unless they actively disable it). That's fine with me, but just realize. If there is a defensible reason to enable it for the installer but not the installed system, then the stage 1 prompt should offer both choices. The problem with not enabling it for the installer is that it is the first interaction any new user has with MGA is the installer, and to have a basic piece of your hardware not work out of the box is really bad PR.
(In reply to Thierry Vignaud from comment #23) > Suse does have this patch: > https://build.opensuse.org/package/view_file/X11:XOrg/xf86-input-libinput/ > n_enable-tapping.patch?expand=1 > > I've no strong opinion on that front. > But I would prefer this to be discussed upstream with Peter Hutterer. > And I want to be sure this would not upset other laptop users. I personally prefer having tap-to-click, but I'd definitely want to see whether Peter would be okay with turning this behavior on by default rather than not having it on by default. If not, I think a reasonable compromise would be to have a query in the installer to turn it on.
CC: (none) => ngompa13
Old behavoir was tap-to-click Various modern handheld devices have only tap-to-click MSwindows have tap-to click as default too, i think. So by both tradition and modern references to me it seem tap-to-click is the normal and expected behaviour. One addition to complexity is that some modern touchpads can be set in bios for simple or advanced modes. I had to set it to simple for it to work in installer, and then change it to advanced to get the advanced functions found in Plasma settings.
Ping ?
Ping again ?
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16575
CC: (none) => knight4553kai
@ LpSolit or Stormi Please block the author of comment 31
CC: (none) => LpSolit, stormi-mageia
CC: LpSolit => (none)
Now that time has passed, I could see that users unused to computers mistankenly click when using the touchpad when tap-to-click is enabled. So this new default is good for them. So closing as upstream decision has good effects.
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED
Sorry Jose, but I'm reopening this. Given that in over 30 comments every commenter (including some heavy hitters) have voiced support for this (or at least no objection), I don't see why you have any justification to unilaterally decide that it's a WONTFIX. I'm lowering the severity to major, since critical isn't really appropriate as this has made it out into the wild. But I still think it should be fixed for MGA8.
Status: RESOLVED => REOPENEDResolution: WONTFIX => (none)Severity: critical => major
I don't see why Mageia's behaviour on the point should be different from all others…
(In reply to Thierry Vignaud from comment #36) > I don't see why Mageia's behaviour on the point should be different from all > others… I'm not sure if that means you agree with most everyone in here that the default should be changed, or if "all others" refers to users of libinput. I'll point out that at least one major distro (SUSE) reverts the libinput default in both their installer and their desktop(s). Of course Windows supports tap-to-click by default, as did OS/2. I don't know for certain, but I'd bet MacOS does too. I think if you want to consider "all others" as libinput users, you have to include only those distros who have opted to leave the defaults in place. I'm not an expert on all distros, but the only one I've come across that does this is Fedora.
Depending on what systems screen i click i expect different behaviour, and i always hesitate... I think default no tap to click (like it is currently) is the most safe but less convenient. So IMHO best disabled on fresh install, but should be easy for normal users to change. Extra point if installer asks like proposed in comment 2. But easily settable on an installed system, per user if possible, is best.
(In reply to Morgan Leijström from comment #38) > But easily settable on an installed system, per user if possible, is best. Plasma > systemsettings > inputs > touchpad > taptoclick
Great, then it is IMO already OK for Plasma :) Someone know how is the support for that in our default setups for Gnome, Cinnamon, Mate, Xfce, LxDE, Enlightenment? (most importantly Gnome and xfce) Nice if it works in all live isos Plasma, Gnome, Xfce.
I know GNOME has a similar setting, don't know about the others. But to get it to work for the DMs you have to mess with xorg.conf, and there's no way to get it for the installer at all.
(In reply to Frank Griffin from comment #41) > I know GNOME has a similar setting, don't know about the others. But to get > it to work for the DMs you have to mess with xorg.conf Wrong : I have never edited an xorg.conf for years, and I use taptoclick in all my laptop that allow it. , and there's no way to get it for the installer at all. Well, in the Live medias, you can do this setting, then launch the installer ;-)
(In reply to José Jorge from comment #42) > (In reply to Frank Griffin from comment #41) > > I know GNOME has a similar setting, don't know about the others. But to get > > it to work for the DMs you have to mess with xorg.conf > > Wrong : I have never edited an xorg.conf for years, and I use taptoclick in > all my laptop that allow it. I think you're confusing the DM (Desktop Managers) and the DE (Desktop Environment). DMs are the login panels like GDM, SDDM, etc. Neither SDDM nor GDM have configuration settings for this. To turn on tap-to-click for the DMs, you have to add an xorg.conf with the proper setting. And if a user turns it on for the DE, he'll be constantly confused that it doesn't work in the DM. At least I find myself tapping in the DM and wondering why it's not responding, and I'm fully aware of this stuff.
Hi, This is High priority bug for a good reason. Making Mageia even better than ever is best direction. In order to do right thing, this bug should be examined and fixed as soon as possible. Packagers, please make the status to Assigned when you are working on this. Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it. On October 1st 2020, we will drop priority to normal.
Once again, it seems like almost everyone who's commented here is either in favor of enabling tap to click or wouldn't object if it were done. While there might be some value to querying the upstream developer about this, the libinput documentation pretty clearly states that their preference is to disable it. And, as already pointed out, at lease one major distro (SUSE) enables it by default whether upstream likes that or not. Can someone please make a decision on this ? Just to minimize development cost, I'd vote for implementing the workaround in comment#1 (or something equivalent if there's a better way to do it) rather than extend the development cost by adding GUI support for enabling/disabling the feature.
Ping ! Don't give up, Frank :) Maybe in the year 2525, we will be able to use a touchpad for what it is designed for.
CC: (none) => shybluenight