they all appear to start fine but the xterm window doesnt show up on all of them.
my first instant thought that something at the builder script went wrong....even after reread template applications nothing changed...
except on the stretch template: after rereading the applications, uxterm was added and is also showing up when i start it from the menu
this lead me to the assumption that building went in general fine and something else is broken....
.xsession-error log shows no errors expect for some scaling issues
but mainly after an "qvm-run -a centos-7-minimal xterm"
i see
"
centos-7-minimal: Starting GUI
centos-7-minimal: Sending monitor layout
"
help for debbuging this and pointing me into the right direction is greatly appreciated ;)
thanks for the hint attaching to the console....login as root needs a password and i didnt set yet any... i could mount the root fs and chroot into it to set one but did i forgott something when building these templates? any recommended procedure to set one?
thank you so much....
you think thats it? so i integrate the passwordless-root in my building process and it should work?
if i do on dom0 a "qvm-run -u root centos-7-minimal passwd" it doesnt return anything...and stuck there with a blinking cursor like any "qvm-run" command
yeah your right, figured that out a bit later...unfortunatly nothing happens after execution the cursor just sits there like the programm (passwd) is open but i cant see nothing on dom0...i have to ctrl+c out and get some python traceback shown in dom0 terminal.
cant see in the build logs folder any passwordless sudo meta package but found some other errors in all of the template building logs could this be related to my error?
"
-> Installing core RPM packages...
/bin/sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
warning: %post(libsepol-2.5-8.1.el7.x86_64) scriptlet failed, exit status 127
Failed to get D-Bus connection: Operation not permitted
"
btw. any easy way to copy+paste logs from dom0 or do i have to copy the files first in a lower lvl domain?
so i put another few hours into troubleshooting and managed to remove some build errors trough solving dependencies, tried the 4.0 and 4.1 stable sources,but still no luck....
so i missed obviously something at the building process?!
Even if the paswordless sudo setup has to be done on minimal templates, i should be able to see and work with a terminal on a fresh created template with qubes-builder i guess?
thanks in advance ;)