Then I tried 5 times to start xterm in a new kali-based dispXXXX as described in my initial post:
1 time out of 5, Xterm opened and I was able to work in my new dispXXXX
4 times out of 5, Xterm did not pop up and the dispXXXX shut down after 2 minutes. Maybe my initial assessment of 50% was too optimistic.
I was able to get an Xterm window by going to Q menu → right-click on dispXXXX → Run Command in Qube → I typed “Xtem”. But that window closed when the VM shut down.
I guess increasing qrexec_timeout to 3600 might give me a dispXXXX for one hour but I do not want my VMs to shutdown unexpectedly (except if I constantly look at the clock) when I work.
Not sure I understand what you mean with “slow start”. Either there is no problem or xterm does not start at all. In the latter case, I can start an xterm window through the Q menu as described above, though, which then opens immediately.
That is precisely my question with this post since I don’t know how to do that:
In Qubes (since I assume a qrexec problem is related to Qubes), where are the logs I should look at?
Is there some documentation explaining qrexec that would help me understand and solve my problem?