Xorg – ignore first click event when resuming from Screen Blanking

I'm not familiar with Cinnamon, but it should be possible to enable your Scroll Lock key.

First, we need to see if you have a spare keyboard modifier slot. Run:

xmodmap -pm

That will print a list of your current modifier setup. Hopefully, one of those lines won't have any keys listed; generally that will be mod3. Assuming that's the case, you can enable Scroll Lock with this command:

xmodmap -e "add mod3 = Scroll_Lock"

Your Scroll Lock LED should now respond to Scroll Lock key presses.

If that works, you probably want X to do that automatically whenever it starts. There are various ways to do that: it can be done on a per user basis, but for something like this I think it makes sense for it to be set globally.

But I've never done this before myself, so I'd better test it before giving further details. :)

OK. The method I tried to activate that modmap globally doesn't work for me on KDE. :( But activating it in my home directory seems to work OK.

Create a file called .Xmodmap in your home directory containing this line:

add mod3 = Scroll_Lock

The easiest way to do that is:

cd ~
echo >.Xmodmap "add mod3 = Scroll_Lock"

Now restart X (logout & login again). Hopefully, your Scroll Lock key will be working. If it doesn't, please let me know.

This is only a partial answer. Other folks should feel free to copy this as a basis for their answers.

Touch screens input devices can be opened as simple mice, or with full access to their touch-screeniness via /dev/input/... and evdev stuff.

You need to get your X server to use the input device as a touchscreen. The X server translates touch-screen events like dragging along the side into mouse-wheel events, for example. Apps that want full gesture (multi-touch) support would need to open the Linux input event device themselves, instead of just getting X11 pointer position / mouse button events.

Kernel drivers for your specific touchscreen should be getting loaded automatically when you plug it in, unless the generic USB mouse driver claims the device first.

Look in your kernel log (dmesg) to see log messages about it. lsusb could help find device ID stuff to search for in the kernel log.