Drivers KDE

Bryant Son - Bryant Jimin Son is a Senior Consultant at Red Hat, a technology company known for its Linux server and opensource contributions. At work, he is working on building the technology for clients leveraging the Red Hat technology stacks like BPM, PAM, Openshift, Ansible, and full stack development using Java, Spring Framework, AngularJS, Material design. Restart KDE Plasma 4. To do this with the Plasma 4 desktop, launch the Terminal window. This is known as Konsole in KDE. Copy and paste the following two commands in the Konsole one by one and hit enter after each.

This article or section is a candidate for merging with Calibrating Touchscreen.

Notes:please use the second argument of the template to provide more detailed indications. (Discuss in Talk:Touchscreen#)

If you ever tried to set up a touchscreen device in linux, you might have noticed that it's either working out of the box (besides some calibration) or is very tedious, especially when it is not supported by the kernel.


This article assumes that your touchscreen device is supported by the kernel (e.g. by the usbtouchscreen module). That means there exists a /dev/input/event* node for your device. Check out

to see if your device is listed or try

for every of your event nodes while touching the display. If you found the corresponding node, it's likely that you will be able to get the device working.

Available X11 drivers

There are a lot of touchscreen input drivers for X11 out there. The most common ones are in the extra repository:

  • xf86-input-evdev (likely the default driver if you plug in your touchscreen and it 'just works')
  • xf86-input-libinput; see also libinput

Less common drivers, not contained in the repository, are:

  • xf86-input-magictouch
  • xf86-input-mutouch
  • xf86-input-plpevtch
  • xf86-input-palmax

Proprietary drivers exist for some devices (e.g.: xf86-input-egalaxAUR), but it's recommended to try the open source drivers first.

Depending on your touchscreen device choose an appropriate driver. Again, evdev is likely to be the default if your touchscreen 'just works.'

Two-fingers scrolling

The two-fingers scrolling has to be implemented on the application side (see this link).For Firefox, see Firefox/Tweaks#Enable touchscreen gestures.

There is a hack to emulates this scrolling behavior for every application in #Touchegg, but the X server still handles it as text selection (at least with Plasma).

evdev drivers


Install xinput_calibratorAUR (AUR). Then, run xinput_calibrator and follow the instructions.

Using a touchscreen in a multi-head setup

To use multiple displays (some of which are touchscreens), you need to tell Xorg the mapping between the touch surface and the screen. This can be achieved with xinput as follows.

Take for example the setup of having a wacom tablet and an external monitor; xrandr shows both displays:

You see we have two displays here. LVDS1 and VGA1. LVDS1 is the display internal to the tablet, and VGA1 is the external monitor. We wish to map our stylus input to LVDS1. So we have to find the ID of the stylus input:

We see that we have two stylus inputs. We now need to simply map our inputs to our output like so:

You can automate this by putting these commands in your ~/.xinitrc or similar. The mapping will be lost if the touchscreen is disconnected and re-connected, for example, when switching monitors via a KVM. In that case it is better to use a udev rule. The Calibrating Touchscreen page has an example udev rule for the case when a transformation matrix has been calculated manually and needs to be applied automatically.

Using xrandr-watch-git to automate map-to-output

Drivers linux

There are xrandr events we can capture from a script. Install xrandr-watch-gitAUR, create a script ~/.xrandr-changed with execution permission to perform map-to-output, for example:

and start, test and enable the systemd/User service xrandr-watcher.service.


Drivers Keep Uninstalling

Touchegg is a multitouch gesture program, only compatible with X, that runs as a user in the background, recognizes gestures, and translates them to more conventional events such as mouse wheel movements, so that you can for example use two fingers to scroll. But it also interferes with applications or window managers which already do their own gesture recognition. If you have both a touchpad and a touchscreen, and if the touchpad driver (such as synaptics or libinput) has been configured not to recognize gestures itself, but to pass through the multi-touch events, then Touchegg will recognize gestures on both: this cannot be configured. In fact it does a better job of recognizing gestures than either the synaptics or libinput touchpad drivers; but on the touchscreen, it's generally better for applications to respond to touch in their own unique ways. Some Qt and GTK applications do that, but they will not be able to if you have Touchegg 'eating' the touch events. So, Touchegg is useful when you are running mainly legacy applications which do not make their own use of touch events.

The two-fingers scrolling has been disabled in the recent rewrite of touchegg 2.0.To enable it, install xdotool and see this closed issue.

Retrieved from ''

July 29th, 2015 Update:
Ok, really wierd. I had marked this as solved after I found adding this to my 20-nvidia.conf fixed the problem

However, I had to reinstall arch and for some reason after the reinstall this will no longer fix the problem.I have gone over everything numerous times now and cannot figure out what is wrong. Running thee command by itself in the terminal also no longer fixes the problem. I have tried re-installing my nvidia drivers and that also does not help. I am wits end and do not know what to do and whats really irritating is the fact that it was working on my other install. Does anyone have any suggestions?
July 31st, 2015 Update:
Ok, even wierder. I couldn't figure out what I had done on my other install to fix things EXCEPT for installing the nouveau drivers and then switching back to nvidia, THEN using:

Drivers Keyboard Lenovo

So I tried switching to he nouveau drivers and then switching back to nvidia and applying the 'Option... {FullCompositionPipeline = On}' and FUCK YES NO TEARING!! So I don't know why but unless I do that there is tearing.

Original post:
I have had screen tearing when watching videos, gaming or sometimes scrolling and have tried everything I could find to fix the problem. I am using the proprietary driver and KDE 4 but I have the issue on plasma 5 and GNOME too and I am so tired of this issue i'm considering getting a new video card. I have a GeForce GTX 970. I have tried reinstalling arch and am all out of ideas.

Nvidia Drivers Kde Plasma

What i've tried:

Adding triplebuffer=1 to /etc/profile.d/

Adding export __GL_YIELD='USLEEP':

I have triplebuffering set to true on my /etc/X11/xorg.conf.d/20-nvidia.conf:

Drivers Kentucky

In my nvidia settings I have allow flipping and sync to vblank checked.

Drivers KDE

Does anyone know how I can fix this?

Last edited by STREBLO (2015-07-31 21:09:05)