Before installing xinput_calibrator (build from source on Porteus linux) I had a custom xmodmap rule file in a couple of user directories. It would work every boot no matter the user. There was persistence on boots where xmodmap would run each boot and include my custom rules file.
Ever since running xinput_calibrator to calibrate the touchscreen on my webdt tablet xmodmap will no longer run on boot. I have scripted xmodmap to start in a 777 file and I can try to call this file in rc.local with a sleep value or via rc4.d in an autostart file.
I have tried to call my startxmodmap file from an exec /usr/bin/xmodmap /home/guest/.Xmodmap in the autostart area in LXDE and it still wont fly. Out of potential start points for this script Each boot I need to connect a usb keyboard to the tablet and issue the command manually if I wish to have mapped keycodes (essential for this tablet as it has a dpad and hard buttons on the front of the tablet.
What can I provide (no experience troubleshooting input events) in order to determine how xmodmap was broken? This was built up from a fresh install and to make sure I started over and produced the same results. xmodmap worked up to calibrating the T/S. Its like something is turning it off no matter how hard I try to get it started.
Before installing xinput_calibrator (build from source on Porteus linux) I had a custom xmodmap rule file in a couple of user directories. It would work every boot no matter the user. There was persistence on boots where xmodmap would run each boot and include my custom rules file.
Ever since running xinput_calibrator to calibrate the touchscreen on my webdt tablet xmodmap will no longer run on boot. I have scripted xmodmap to start in a 777 file and I can try to call this file in rc.local with a sleep value or via rc4.d in an autostart file.
I have tried to call my startxmodmap file from an exec /usr/bin/xmodmap /home/guest/.Xmodmap in the autostart area in LXDE and it still wont fly. Out of potential start points for this script Each boot I need to connect a usb keyboard to the tablet and issue the command manually if I wish to have mapped keycodes (essential for this tablet as it has a dpad and hard buttons on the front of the tablet.
What can I provide (no experience troubleshooting input events) in order to determine how xmodmap was broken? This was built up from a fresh install and to make sure I started over and produced the same results. xmodmap worked up to calibrating the T/S. Its like something is turning it off no matter how hard I try to get it started.
Thank you in advance Daryl