Hello I have just bought a KDE 101 Slimbook
When I go to Touchpad Settings I see "No touchpad found"
How can I configure the touchpad? (it's way to sensitive and impossible to use comfortably)

Right click any where on the screen, then choose Run Command, or Alt + Space bar, and type "Touchpad". Then you can adjust it there.

Hey chaps,

I have this issue too, on the same machine. (KDE Slimbook 13" running KDE Neon 5.10 Release 16.04)

@fredhoud, the combination you are speaking about open the Touchpad System Setting Module. Within it, it display "No touchpad found".

More worrisome, the pointer sometime completely freeze, clicking might or might not be possible until.. rebooting.

@Fenneck,
Hummm.... We have 4 laptops with Neon. Two of them KDE neon 5.10, and the other two with KDE neon LTS 5.8. I checked all of them, and I can change the Touchpad configuration, and or speed with no problem. Surely KDE Slimbook comes with some kind of support, doesn't it?

Hello everyone.

I also bought a Slimbook KDE and encounter this message in Systemsettings. Slimbook provides an application to manage specific hardware of the computer (touchpad is not a synaptics touchpad and it seems that Ubuntu doesn't support non synaptics touchpads) but this application is in spanish. I didn't see where to configure the touchpad with this app, only enable/disable it.

This app is located in K menu>Applications>Utilities or System (I don't remember).

Hi there! It seems there is a bug reported by Slimbook here : https://bugs.launchpad.net/ubuntu/+sour ... ug/1688625

Problem comes from kernel which not recognize the touchpad correctly (if I well understand). We have to wait...

Hi sorry I missed these replies!
I got my touchpad to work on my Slimbook, however it's quite bad!
The motion is very choppy and unusable and the touchpad doesn't sense the lower part of the pad at all

I have the same problem with a kde slimbook I just bought. Maybe worth noting is that I made a fresh install of neon LTS on it (the default install would make a black screen when starting sddm and restarting it was not helping).

The symptoms are:

* the touchpad is not recognized as a touchpad in kde system settings
* the touchpad will sometime stop working during a session (hibernating and coming back is enough to make it works again)

Those are probably two unrelated problems, though.

Actually, I think the kernel recognizes the touchpad as such, because it allows to scroll with two fingers (or maybe that's a default behavior? Not like we would have noticed, we can't click at two different places at the same time with a mouse).

This is still annoying, though, because we can't use the feature to deactivate touchpad while we're typing on the keyboard (so I keep jumping randomly in my file while I writing code, because my thumbs touch the touchpad).

X is reporting the device as a PS/2 mouse:

```
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ImExPS/2 Generic Explorer Mouse id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ USB 2.0 PC Cam id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ 00:02:3C:4A:BC:55 id=12 [slave keyboard (3)]
```

I tried the applet provided by Slimbook [1], but it did not help. Reading its code, it first makes a driver detection by checking man page presence [2] (that's unusual ), then, in my case, tries to use synclient, ultimately starting syndaemon asking it to set the delay [3].

When I try to start syndaemon myself with `syndaemon -k -i 2000 -d` (within a X session), I get an exit status 2 which, from man page, means that "the connection to the X sever could not be established or no touchpad device could be found", its pretty safe to assume that's an error about not recognizing the device as touchpad.

Now, at this point, it's worth asking: has that anything to do with KDE? I guess that at the very least, given KDE is advertising slimbooks as linux friendly laptops, it's a bit related But more seriously, maybe plasma could try to implement its own mean to deactivate mouse while typing on the keyboard? This would go a long way regarding usability, and would cover any other "not recognized as touchpad" problem in the future. Sorry, I would love to help on this, but I'm not used to C++ (I guess there's no mean to contribute with golang?).

Also, in favor of a software solution, it does not seem to me from the discussion between slimbook and ubuntu that it's something about to find a solution [4].


[1] https://github.com/slimbook/slimbook-touchpad
[2] https://github.com/slimbook/slimbook-to ... erences.py
[3] https://github.com/slimbook/slimbook-to ... nces3#L307
[4] https://bugs.launchpad.net/ubuntu/+sour ... ug/1688625

Thinking about it twice, is there any dbus or other ipc interface I could plug in to receive keyboard events, and any mean to disable/enable mouse (through /sys, maybe?)? I could write something to implement the feature as a standalone program before it's implemented within plasma / if it won't be implemented.

Ok, I've made a quick app to fix this: https://github.com/oelmekki/grumpy_cat

The only way I found to disable/enable mouse is to unload/load mouse module, so this is highly inefficient. But will do until we have better.