As in a lot of other bug reports, tap-to-click is not enabled by default any more in various system components. This one is about SDDM, which has no GUI configuration mechanism for changing this (or any other) setting. Tap-to-click has been enabled everywhere in MGA since forever. If some upstream genius has suddenly taken a dislike to it, I think we should enable it by default everywhere and see what arguments, if any, anyone can advance for reverting the change. Reproducible: Steps to Reproduce:
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16942
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16575
Ping ?
This is nothing specific to the display manager, but related to the default settings for your touchpad/clickpad and for the X server. What does "synclient -l" say and what touchpad do you have? Anything special in xorg.conf or in xorg.conf.d/ ? You may want to have a look at the default settings (udev rules and xorg config) from x11-driver-input-synaptics
CC: (none) => doktor5000
This is very confusing. The x11 synaptics driver is installed, but [root@ftglap rules.d]# syndaemon No synaptics properties on device 'SynPS/2 Synaptics TouchPad'. [root@ftglap rules.d]# synclient -l Couldn't find synaptics properties. No synaptics driver loaded? There is nothing related to synaptics in xorg.conf or xorg.conf.d. The udev rules for synaptics are virtually nonexistent and those for touchpad are extremely device-specific. I assume that the reason synclient fails is that syndaemon isn't running, but I have no idea what is supposed to start it or why the driver it's looking for isn't loaded. Nor do I have any idea why if, in plasma5, I use system services to enable tap-to-click it works, but still has no effect on the DM or GNOME. It used to be really simple: xorg.conf ruled the roost, and everything obeyed it. Then people started moving responsibilities around and duplicating functions, and now it's not clear who is supposed to do what and when and with what. I don't know if the problem here is that some module should be in dracut or modprobe'd and isn't, or whether there's a systemd service that should be enabled and isn't, or whether there should be udev rules and aren't, or whether stuff should be in xorg.conf and isn't being put there.
Frank, can you please add the following to a new file named /etc/X11/xorg.conf.d/10-synaptics.conf # /etc/X11/xorg.conf.d/10-synaptics.conf Section "InputClass" Identifier "touchpad catchall" Driver "synaptics" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3" Option "ClickPad" "true" Option "EmulateMidButtonTime" "0" Option "AreaBottomEdge" "4000" Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0" EndSection I'm not 100% sure, but I think it's to do with some X server updates, the above will fix it in almost all cases. Need to look at getting this included in the correct package before release 6 too.
CC: (none) => luke.nukem.jones
Hi Luke, That enables tap-to-click for SDDM perfectly. However, it interferes with the Plasma settings in the way described in bug#16940. I've been told in the past that xorg.conf is passe, and at one point it was recommended that I delete it and run X without it. I think the various components that fool with this really need to decide who's going to be in control.
(In reply to Frank Griffin from comment #5) > I've been told in the past that xorg.conf is passe, and at one point it was > recommended that I delete it and run X without it. Well, usually X server is left to autodetect everything, but you can still enforce settings via xorg.conf, that is still the usual way - as e.g. drakx11 does to set the graphics driver, or like the . Also see the defaults from /usr/share/X11/xorg.conf.d/ that are taken into account. Not sure why synaptics driver didn't work for you, maybe your touchpad needs a patch to be recognised or some other quirks - that's why I asked which model it is. Also see https://wiki.archlinux.org/index.php/Touchpad_Synaptics for some overall in-depth information on this topic. And FWIW if you say the defaults are broken regarding touchpads they should be fixed, no matter what upstream says. Our users matter, IMHO.
The touchpad is a "SynPS/2 Synaptics TouchPad", vendor ID 0x0002 device ID 0x0007.
@ Frank Assigning to SDDM maintainer now Is this bug still valid?
Keywords: (none) => NEEDINFOCC: (none) => marja11Assignee: bugsquad => mageia
Yes.
The cause of this is not SDDM, which appears to be following standard xorg.conf directives. Please see https://bugs.mageia.org/show_bug.cgi?id=18972 , which gives details of how to override the libinput default of disabling tap-to-click. If the workaround in https://bugs.mageia.org/show_bug.cgi?id=18972 is applied, tap-to-click is enabled in SDDM.
Status: NEW => RESOLVEDResolution: (none) => INVALID