Am 30.07.2018 um 11:56 schrieb richard lucassen:
On Fri, 27 Jul 2018 10:57:48 -0400 "John Stoffel" <john@stoffel.org> wrote:
It sounds like when the script runs, the Xserver isn't quite ready, and xmodmap is waiting for that. Maybe you can start debugging by putting:
Hmm, this is a Q&D workaround:
$ cat /usr/lib/x2go/extensions/post-resume.d/010_xmodmap #!/bin/dash test -f ~/.Xmodmap || exit 0 /usr/local/scripts/xmodmap.sh &
$ cat /usr/local/scripts/xmodmap.sh #!/bin/dash sleep 10 exec /usr/bin/xmodmap ${HOME}/.Xmodmap
You should be able to simplify that into one script, assuming dash understands the syntax bash uses for this (haven't tried it):
$ cat /usr/lib/x2go/extensions/post-resume.d/010_xmodmap #!/bin/dash test -f ~/.Xmodmap || exit 0 (sleep 10; exec /usr/bin/xmodmap ${HOME}/.Xmodmap) &
Not sure why you'd need the "exec", even.
Instead of blindly sleeping 10 seconds, you could also check if xmodmap returns an error when it's called too early in the process. Maybe something like (while ! /usr/bin/xmodmap ${HOME}/.Xmodmap ; do sleep 1 ; done) &
Also, is there a particular reason why you need to run xmodmap manually/scripted, rather than using the keyboard settings option inside X2GoClient? Are you a macOS X2GoClient user, and the autodetection we need to use on the Mac is failing for you?
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243