Hi!
My x2go-TCE actually works. But if I then want to continue to work the next day to the system, the client loads for several minutes until it breaks then with the message
######## ... "Kernel panic - not syncing: Attempted to kill init! ... "Pid: 1, comm: init Not tainted 3.2.0-486 # 1 Debian 3..68-1 + deb" ... "Call Trace" ... "? Panic + 0x4D / 0x139" ... "Do_exit? + 0x75 / 0x598" ... "Do_group_exit? + 0x48 / 0x6B" ... "Sys_exit_group? + 0x11 / 0x11" ... "? Syscall_call + 0x7 / 0x7" ########
A VM that I use as a thin client for testing, writes the same lines, and behind it yet:
######## ... "atkbd serio0: Spurious ACK on isa0060 / serio0 Some Program Might Be Trying access hardware directly." ########
The whole happens if I the next day again test the system, so turn on a client and the system is loaded. The day before, it was always perfect.
I've written in the /srv/tftp/x2go-tce.cfg: ######## APPEND .... SELINUX = permissive SELINUXTYPE = permissive ########
After that it was not working for one start, but after that the error comes again.
If rebooting the server, the problem is resolved, but the next day it's back.
It would be nice if someone would help me.
Olaf
(PS: Stefan, thank you for your help in the article "Writing through dangling symlink ...", that was the solution. I just do not get how I can respond to the contribution from you on gmane..)