Description of problem: My ELAN Touchscreen behaves in GNOME (ver 3.14.2) as a mouse. That means that the most native gestures are not recognized and for example scrolling in nautilus doesn't work. Also chromium which has a native multitouch support doesn't recognize any touchscreen device. Even if I pass the device with "chromium-browser --touch-device=12" chromium treats the touchscreen as a mouse and scrolling and similar doesn't work. Configuration with the relevant drakconf tool did not help, too... Also in harddrake the touchscreen device is listed under "mouse" and module is "mouse1".. Here the relevant content of XOrg.0.log: [ 29.852] (II) config/udev: Adding input device ELAN Touchscreen (/dev/input/event12) [ 29.852] (**) ELAN Touchscreen: Applying InputClass "evdev touchscreen catchall" [ 29.852] (II) Using input driver 'evdev' for 'ELAN Touchscreen' [ 29.852] (**) ELAN Touchscreen: always reports core events [ 29.852] (**) evdev: ELAN Touchscreen: Device: "/dev/input/event12" [ 29.853] (--) evdev: ELAN Touchscreen: Vendor 0x4f3 Product 0x307 [ 29.853] (--) evdev: ELAN Touchscreen: Found absolute axes [ 29.853] (--) evdev: ELAN Touchscreen: Found x and y absolute axes [ 29.853] (--) evdev: ELAN Touchscreen: Found absolute touchscreen [ 29.853] (II) evdev: ELAN Touchscreen: Configuring as touchscreen [ 29.853] (**) evdev: ELAN Touchscreen: YAxisMapping: buttons 4 and 5 [ 29.853] (**) evdev: ELAN Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 29.853] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:04F3:0307.0001/input/input13/event12" [ 29.853] (II) XINPUT: Adding extended input device "ELAN Touchscreen" (type: TOUCHSCREEN, id 11) [ 29.853] (II) evdev: ELAN Touchscreen: initialized for absolute axes. [ 29.854] (**) ELAN Touchscreen: (accel) keeping acceleration scheme 1 [ 29.854] (**) ELAN Touchscreen: (accel) acceleration profile 0 [ 29.854] (**) ELAN Touchscreen: (accel) acceleration factor: 2.000 [ 29.854] (**) ELAN Touchscreen: (accel) acceleration threshold: 4 [ 29.855] (II) config/udev: Adding input device ELAN Touchscreen (/dev/input/mouse1) [ 29.855] (II) No input driver specified, ignoring this device. [ 29.855] (II) This device may have been added with another device file. It would be great if someone could help... If you need further informations please let me know! Version-Release number of selected component (if applicable): How reproducible: Try scrolling with touchscreen in chromium Steps to Reproduce: 1. Open chromium (ver: 51.0.2704.103 ) 2. Try to scroll with the touchscreen or go back with drag to the left
(not sure I'm assigning to the right persion, please re-assign if needed)
CC: (none) => marja11, thierry.vignaudAssignee: bugsquad => tmb
Please attach (do not paste it) the lspcidrake.txt file resulting from running the following command: lspcidrake -v > /tmp/lspcidrake.txt Also please attach the whole X.org logs. Last but not least what's the output of the following command: rpm -qa x11-driver'*'|sort
Keywords: (none) => NEEDINFO
Created attachment 8120 [details] The output of the command lspcidrake -v
Created attachment 8121 [details] the whole Xorg.0.log
Dear Thierry, Thank for your answer. Enclosed you find the output of "rpm -qa x11-driver'*' | sort": [maximilian@localhost ~]$ rpm -qa x11-driver'*' | sort x11-driver-input-1.0.0-20.mga5 x11-driver-input-acecad-1.5.0-16.mga5 x11-driver-input-aiptek-1.4.1-14.mga5 x11-driver-input-evdev-2.9.1-1.mga5 x11-driver-input-evtouch-0.8.8-22.mga5 x11-driver-input-fpit-1.4.0-16.mga5 x11-driver-input-hyperpen-1.4.1-20.mga5 x11-driver-input-joystick-1.6.2-9.mga5 x11-driver-input-keyboard-1.8.0-7.mga5 x11-driver-input-mouse-1.9.1-3.mga5 x11-driver-input-mutouch-1.3.0-16.mga5 x11-driver-input-penmount-1.5.0-16.mga5 x11-driver-input-synaptics-1.8.1-4.mga5 x11-driver-input-void-1.4.0-16.mga5 x11-driver-input-wacom-0.26.1-2.mga5 x11-driver-video-7.7-6.mga5 x11-driver-video-ati-7.5.0-3.mga5 x11-driver-video-cirrus-1.5.2-10.mga5 x11-driver-video-fbdev-0.4.4-12.mga5 x11-driver-video-glint-1.2.8-13.mga5 x11-driver-video-intel-2.99.917-14.2.mga5 x11-driver-video-mach64-6.9.4-13.mga5 x11-driver-video-mga-1.6.4-1.mga5 x11-driver-video-neomagic-1.2.8-8.mga5 x11-driver-video-nouveau-1.0.11-5.mga5 x11-driver-video-openchrome-0.3.3-12.mga5 x11-driver-video-qxl-0.1.4-1.mga5 x11-driver-video-r128-6.9.2-9.mga5 x11-driver-video-s3-0.6.5-11.mga5 x11-driver-video-s3virge-1.10.6-11.mga5 x11-driver-video-savage-2.3.7-9.mga5 x11-driver-video-sis-0.10.7-16.mga5 x11-driver-video-sisimedia-0.9.1-6.20091203.20.mga5 x11-driver-video-sisusb-0.9.6-11.mga5 x11-driver-video-tdfx-1.4.5-12.mga5 x11-driver-video-trident-1.3.6-12.mga5 x11-driver-video-v4l-0.2.0-24.mga5 x11-driver-video-vesa-2.3.3-8.mga5 x11-driver-video-vmware-13.1.0-1.mga5
Attachment 8121 mime type: text/x-log => text/plain
Older reports seems to point to kernel...
Source RPM: (none) => kernel?
Keywords: NEEDINFO => (none)
I don't know if it is helpful, but I will attach also the Xorg.0.log from my mageia 6 test install where the touchscreen works out of the box. If it doesn't help, please be free to remove the file... @Thierry Vignaud which older reports do you mean? I didn't find anything about this issues...
Created attachment 8122 [details] Xorg.0.log from the mageia 6 install where the touchscreen works without problems!
(In reply to Max Perl from comment #7) I meant reports in other distros :-) (In reply to Max Perl from comment #8) The difference is that I made mga6 default to using libinput And indeed, we can see in your logs: + (II) Using input driver 'libinput' for 'ELAN Touchscreen' Can you try installing x11-driver-input-libinput on your mga5 box & restart the system?
Dear Thierry, Thanks a lot!!!!!! This was the issue. After installing x11-driver-input-libinput and restarting everything works fine! I am very happy :-) Would it be possible to install the libinput driver automatically at the installation or the first update after installation so that the touchscreen works out of the box? This would be a very big help for beginners... Again Thank you very much!
Status: NEW => RESOLVEDResolution: (none) => FIXED
As I said in comment #9, I've already done that for incoming Mageia 6