New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DispVMs are autodestroyed if default terminal is changed from xterm #3180

Closed
Yethal opened this Issue Oct 16, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@Yethal

Yethal commented Oct 16, 2017

Qubes OS version:

3.2

Affected TemplateVMs:

issue does not seem to be template dependent


Steps to reproduce the behavior:

  1. Go to /usr/local/share/applications
  2. Open qubes-dispvm-xterm.desktop file
  3. Change Exec from xterm to gnome-terminal
  4. Save changes
  5. Start terminal in a dispvm

Expected behavior:

VM is started and gnome-terminal stays open until closed by the user.

Actual behavior:

VM is started and gnome-terminal is launched however after a second it selfdestructs.

General notes:

I assume the whatever mechanism is responsible for destroying the VM has a hardcoded check for xterm. If that's the case, documenting its location seems sufficient.

Related issues:

@Yethal Yethal changed the title from DispVMs are autodestroyed if default terminal is changed from xterm to gnome-terminal to DispVMs are autodestroyed if default terminal is changed from xterm Oct 16, 2017

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 16, 2017

Member

I assume the whatever mechanism is responsible for destroying the VM has a hardcoded check for xterm. If that's the case, documenting its location seems sufficient.

No, the problem is when you start gnome-terminal, it ends immediately, even though actual terminal is still running (hosted by gnome-terminal-server process). You can see this behavior by starting gnome-terminal from another terminal.
Since DispVM is destroyed immediately after its "main application" exits, gnome-terminal is not suitable for this use, unfortunately.

Member

marmarek commented Oct 16, 2017

I assume the whatever mechanism is responsible for destroying the VM has a hardcoded check for xterm. If that's the case, documenting its location seems sufficient.

No, the problem is when you start gnome-terminal, it ends immediately, even though actual terminal is still running (hosted by gnome-terminal-server process). You can see this behavior by starting gnome-terminal from another terminal.
Since DispVM is destroyed immediately after its "main application" exits, gnome-terminal is not suitable for this use, unfortunately.

@marmarek marmarek closed this Oct 16, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment