Question

How can I disable OS-level keyboard shortcuts (e.g. Alt-Tab, Ctrl-Alt-Left/Right, etc.) on a [Ubuntu] Linux machine? I’m developing a full-screen Java Swing app and don’t want the user to be able to task switch away from the program arbitrarily. It’s not enough to toggle the “always on top” flag; users mustn’t be allowed to switch workspaces, migrate focus or any other such things. The machine must function normally before and after the application is executed. Google says that this will require JNI or JNA but I’m looking for a bit more hand-holding.

Answer 1

There’s no point in trying to do this in your application because any of these changes are going to need to be handled by X11 and/or the window manager since those are what respond to the commands. Assuming that you have control of the platform, choose a window manager which supports a kiosk mode. Then use the window manager’s settings to start your application and enter kiosk mode.

Options for window managers which can do this include KDE or twm-kiosk.

(And if you don’t have control of the platform, you’re not likely to be able to have your application intercept things like ctrl-alt-backspace anyway.)

Edit:

In response to a scaled-down version of the question in which he’s willing to let things like ctl-alt-backspace go and just wants most of the keys including alt-tab or other similar application switching key combinations, the following should work:

You should be able to do this using XLib’s XGrabKeyboard method through JNI. This Java/XLib JNI keypress capture tutorial should be a good starting point. However, it uses XGrabKey which just passively listens for keys and does not prevent other applications from receiving them. You’ll instead want to use XGrabKeyboard which actively snags all of the normal keyboard events (which, if the premise of this StackOverflow question is correct, includes the task switching keys).

Note that as a side-effect, key capture in Swing will also probably stop working because your Swing windows are going to be separate from the window you create in C. As such, you will probably have to use your JNI interface to get key presses to your program when needed. (Although I would definitely advise testing it first before writing the code.) You might be able to avoid this if you can get the window using Java AWT Native Interface to get the window ID. (Note that Swing is built on top of AWT, so this will work for Swing.) However, I’m not sure how to do this. It looks like you might be able to navigate the window tree by getting the root window from the Display and going from there to find your Window, but it’s all kind of weird. It would be nice if the AWT NI just told you the window ID, but it doesn’t look like it does that.

As this warning Reminder: XGrabKeyboard is not a security interface notes, this doesn’t make it impossible for other programs to see the keys, but it seems likely that window managers will not be using XQueryKeyMap so it is likely to prevent task switching.