| Summary: | KDE upgrade in cauldron breaks synaptics support | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | RPM Packages | Assignee: | Nicolas Lécureuil <mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | admel.mga, albonis, krnekit, lmenut |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kcm_touchpad | CVE: | |
| Status comment: | |||
|
Samuel Verschelde
2015-06-30 09:22:59 CEST
CC:
(none) =>
lmenut Confirm this. I also have touchpad only reacting to cursor movements after update to mga6. I have kcm-touchpad 1.0 installed and in KDE Control Center it displays error message: "Synaptics driver is not installed (or is not used)". x11-driver-input-synaptics-1.8.2-1.mga6 package is installed. CC:
(none) =>
krnekit Morning, I re-up this topic with a new screen. Inside it's shown what appears on my Cauldron and a fresh new one install on a VM : http://www.cjoint.com/doc/16_02/FBAv5jwT4U8_Screenshot-20160225-164130.png As them, I can't custom the configuration of the touchpad but it's works as Frank Griffin has describe. I didn't have tried solution proposed by Frank Griffin. $ rpm -qa|grep synaptics x11-driver-input-synaptics-1.8.3-4.mga6 $ rpm -qa|grep kcm_touchpad kcm_touchpad-0.3.1-14.mga6 CC:
(none) =>
antoine.dumondel Hello, On a Dell vostro 1510, I have the same behavior : no tap click from the touchpad. most of the options to configure the touchpad in systemsettings5 are indeed greyed out. And MCC is useless on this issue. Here is an extract of Xorg logs : 32.122] (II) config/udev: Adding input device AlpsPS/2 ALPS GlidePoint (/dev/input/event9) [ 32.122] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "evdev touchpad catchall" [ 32.122] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "touchpad catchall" [ 32.122] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "Default clickpad buttons" [ 32.122] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "libinput touchpad catchall" [ 32.122] (II) Using input driver 'libinput' for 'AlpsPS/2 ALPS GlidePoint' [ 32.122] (**) AlpsPS/2 ALPS GlidePoint: always reports core events [ 32.122] (**) Option "Device" "/dev/input/event9" [ 32.122] (**) Option "_source" "server/udev" [ 32.123] (II) input device 'AlpsPS/2 ALPS GlidePoint', /dev/input/event9 is tagged by udev as: Touchpad [ 32.123] (II) input device 'AlpsPS/2 ALPS GlidePoint', /dev/input/event9 is a touchpad [ 32.130] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event9" [ 32.130] (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS GlidePoint" (type: TOUCHPAD, id 12) [ 32.130] (**) Option "AccelerationScheme" "none" [ 32.130] (**) AlpsPS/2 ALPS GlidePoint: (accel) selected scheme none/0 [ 32.130] (**) AlpsPS/2 ALPS GlidePoint: (accel) acceleration factor: 2.000 [ 32.130] (**) AlpsPS/2 ALPS GlidePoint: (accel) acceleration threshold: 4 [ 32.131] (II) input device 'AlpsPS/2 ALPS GlidePoint', /dev/input/event9 is tagged by udev as: Touchpad [ 32.131] (II) input device 'AlpsPS/2 ALPS GlidePoint', /dev/input/event9 is a touchpad [ 32.131] (II) config/udev: Adding input device AlpsPS/2 ALPS GlidePoint (/dev/input/mouse0) CC:
(none) =>
albonis This hasn't been a problem for me for quite a while. I'm not quite sure what fixed it, (In reply to Frank Griffin from comment #4) > This hasn't been a problem for me for quite a while. I'm not quite sure > what fixed it, Well, isn't it the /etc/X11/xorg.conf.d/synaptics.conf you added that fixed it for you ? No, my current /etc/X11/xorg.conf.d has no synaptics.conf, although it has a synaptics.conf.dead with the contents:
# /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
In any case, it's not being used.
Thank's for your answer, Frank. Oh well, my bad, even if most of the features are greyed out in systemsettings5, actually, ticking the box "émulations du clic de la souris" (mouse click emulation) activates the tap click feature. Though, it's the first time i need to activate manually this feature. By the way, if it works, maybe this bug could be closed ? OK. Status:
NEW =>
RESOLVED |
The latest cauldron KDE upgrade cripples synaptics support. Specifically, it fails to load drivers which allow KDE to identify the touchpad. I rebooted my laptop today after several "urpmi --auto-update" runs, and found the support broken. The KDE -> Input Devices -> Touchpad display shows "Touchpad: Unknown Device" and has all of the touchpad configuration options greyed out. The touchpad works for mouse cursor navigation, but tap-to-click and vertical scrolling are disabled and can't be enabled. I finally worked around this by adding an /etc/X11/xorg.conf.d/synaptics.conf file with the following contents: Section "InputClass" Identifier "Touchpad" MatchIsTouchpad "yes" Driver "synaptics" Option "MinSpeed" "0.4" Option "MaxSpeed" "0.9" Option "AccelFactor" "0" Option "TapButton1" "1" Option "TapButton2" "3" Option "VertTwoFingerScroll" "0" Option "HorizTwoFingerScroll" "0" Option "VertEdgeScroll" "1" Option "CoastingSpeed" "8" Option "CornerCoasting" "1" Option "TouchpadOff " "0" EndSection This re-enabled all of the behaviors that I had previously specified in kcmtouchpadrc just as before. Poking around in /etc/X11, I noticed that I had an xorg.conf.old and a new xorg.conf with a timestamp matching the reboot. Neither of them had a section like the one above, and they looked fairly identical to me. Moreover, when I tried to use harddrake2 from drakconf to probe matters, it told me that kcm_touchpad had to be installed. I allowed that, but it didn't help. When I probed later using rpmdrake, I found that there were two versions of kcm_touchpad in the repository. Harddrake2 had chosen the one with the earlier package timestamp, and when I selected the later one it replaced the earlier one. Neither package resulted in KDE being able to see the touchpad. I've previously been told that xorg.conf is passe, and that it shouldn't be there at all (posts by Felix Miata about monitor firmware errors), so while adding the [InputClass] section worked, I'm not sure whether that's the correct or even optimum solution for an MGA6 system. As the xorg.conf.old had no such section, I'm wondering what used to load the synaptics driver and no longer does. Reproducible: Steps to Reproduce: