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

If .bashrc has error, AppVM starting hangs after Waiting for qubes-session #2356

Closed
greenrd opened this Issue Oct 2, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@greenrd

greenrd commented Oct 2, 2016

Qubes OS version (e.g., R3.1):

R3.1

Affected TemplateVMs (e.g., fedora-23, if applicable):

fedora-23


Expected behavior:

If I try to source a nonexistent file in my .bashrc inside a VM, the VM should still start.

Actual behavior:

qvm-start vmname hangs after Waiting for qubes-session... and no applications can be started.

Steps to reproduce the behavior:

  1. Inside an AppVM terminal: echo "source /non/existent/file" >>~/.bashrc
  2. restart AppVM

General notes:

This means .bashrc prints to stderr - maybe some brittle code is looking for something on stderr and not expecting that?

@andrewdavidwong andrewdavidwong added this to the Release 3.1 milestone Oct 2, 2016

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Oct 3, 2016

Member

@greenrd I wonder how you are starting the qube: from the menu?
I think that the qube does start: can you check with qvm-ls

Also, try qvm-run qube xterm - you should see a terminal open with bash error.
Most other commands seem to work as expected when run with qvm-run -a. Can you confirm?

Member

unman commented Oct 3, 2016

@greenrd I wonder how you are starting the qube: from the menu?
I think that the qube does start: can you check with qvm-ls

Also, try qvm-run qube xterm - you should see a terminal open with bash error.
Most other commands seem to work as expected when run with qvm-run -a. Can you confirm?

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Oct 8, 2016

Member

@greenrd @andrewdavidwong
I simply can't reproduce this issue.
I've tried on both 3.1 and 3.2, with various templates, and don't encounter this problem. The reported case of fedora-23 on (clean) 3.1 works for me. The qube starts fine.
Terminal started with qvm-run -a starts the qube, and the terminal opens showing a bash error message as expected.
Can any one else confirm?

Member

unman commented Oct 8, 2016

@greenrd @andrewdavidwong
I simply can't reproduce this issue.
I've tried on both 3.1 and 3.2, with various templates, and don't encounter this problem. The reported case of fedora-23 on (clean) 3.1 works for me. The qube starts fine.
Terminal started with qvm-run -a starts the qube, and the terminal opens showing a bash error message as expected.
Can any one else confirm?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 9, 2016

Member

I, too, am unable to reproduce this. Closing.

Member

andrewdavidwong commented Oct 9, 2016

I, too, am unable to reproduce this. Closing.

@andrewdavidwong andrewdavidwong added notanissue and removed bug labels Oct 9, 2016

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