/qubes-issues

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

Sending ctrl+c to qubes-manager makes it alive but non-functional #1682

Closed
greenrd opened this Issue Jan 23, 2016 · 0 comments

Comments

Assignees

@marmarta marmarta

Labels
Projects
Bugs in Qubes Manager GUI & UX
Milestone
  Release 3.2 updates
4 participants
@greenrd @marmarek @andrewdavidwong @marmarta
@greenrd

greenrd commented Jan 23, 2016

If you press Ctrl+C in a terminal that was used to launch qubes-manager, an error dialog pops up complaining about a keyboardinterrupt, but qubes-manager does not quit. However, it then no longer notices that a VM has been started. It's then necessary to quit and restart qubes-manager.

@marmarek marmarek added bug C: qubes-manager P: minor labels Jan 23, 2016

@marmarek marmarek added this to the Release 3.0 updates milestone Jan 23, 2016

@marmarek marmarek modified the milestones: Release 3.0 updates, Release 3.1 updates Nov 19, 2016

@andrewdavidwong andrewdavidwong modified the milestones: Release 3.1 updates, Release 3.2 updates May 31, 2017

marmarta added a commit to marmarta/qubes-manager that referenced this issue Jul 12, 2018

@marmarta
Correct handling for SIGINT in Qubes Manager 
Instead of killing only one thread, now SIGINT will correctly
exit the entire app.

fixes QubesOS/qubes-issues#1682
Verified
This commit was signed with a verified signature.
@marmarta marmarta Marta Marczykowska-Górecka
GPG key ID: 9A752C30B26FD04B Learn about signing commits
560c54e

@marmarta marmarta referenced this issue in QubesOS/qubes-manager Jul 12, 2018

Merged

Correct handling for SIGINT in Qubes Manager #104

@marmarek marmarek assigned marmarta Jul 14, 2018

@marmarek marmarek closed this Jul 14, 2018

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