Hi Frederic, Although a long time ago, the problem still exists. The solution is to delay the start of Xpad in sufficient time, that the Window Manager is up and running.
A possible workaround can be found here. https://bugs.launchpad.net/xpad/+bug/405314 A possible solution is planned for v4.3 by adding a option for autostarting Xpad from the application, who takes care of this delay. https://launchpad.net/xpad/+milestone/4.3 Cheers, Arthur Borsboom. -- Arthur Borsboom Appartment 10-01 (level 10, app 1) Avenida Arequipa 4130 Lima, Peru Mob: +51 984 230 576 Email: arthurborsb...@gmail.com
