> No, checking again if I put multimedia dependent from
> works, so the problem is the template.
> Last thing I did with the template was install a custom
> connected with the template. I did not know that this may
end damaging the
Disposable VM settings shouldn't affect the template. What
you try to run nautilus from a terminal session to
"multimedia"? If it
doesn't start, that's the issue.
Cannot test it because neither gnome-terminal nor term start,
so? Anyway I prepared a new template, reinstalled everything,
even the printer, and it works, but now I am scared by the
custom dvm thing.
The way to test things like this is to use "qvm-run -p <appvm>
program-name" and watch what errors bome back through that pipe.
Usually you will see something like "program not found" or some
error finding some basic resource that is required.
With dvm's this *is* more of a problem, but doing that same command
against its base templatevm might also give some insightful clues.
I already tried qvm-run at the beginning of this thread, but it gives to reply, no error, nothing. it just froze trying to do that. Only CTRL c works to go on. Now tried to add -p as you suggested, but the result is the same.
Tried xterm, term, gnome-terminal, nothing works. Well the problem is solved because I prepared a new template, but it is good to remember to make a copy of the template before doing things that can break it.
I wonder: What happens if you run "journalctl -b -f" in multimedia while you try executing the commands?