Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up"qrexec not connected" warning flag not cleared despite qrexec later connected ok #878
Comments
marmarek
added this to the Release 2 milestone
Mar 8, 2015
marmarek
added
bug
C: qubes-manager
P: minor
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 8, 2015
Member
Comment by marmarek on 3 Jul 2014 02:18 UTC
What is the exact warning flag text? I've just tried and "Error starting VM: Cannot execute qrexec-daemon!" is cleared correctly.
|
Comment by marmarek on 3 Jul 2014 02:18 UTC |
marmarek
self-assigned this
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 6 Jul 2014 11:49 UTC |
marmarek
modified the milestones:
Release 2.1 (post R2),
Release 2
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ramtej
commented
Nov 21, 2015
|
same issue here. Any ideas ? |
marmarek
modified the milestones:
Release 3.1 updates,
Release 2.0 updates
Nov 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
unman
Apr 14, 2017
Member
@andrewdavidwong Haven't been able to test this - please change milestone to 3.2
|
@andrewdavidwong Haven't been able to test this - please change milestone to 3.2 |
andrewdavidwong
modified the milestones:
Release 3.2 updates,
Release 3.1 updates
Apr 14, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by joanna on 3 Jul 2014 00:26 UTC
None
Migrated-From: https://wiki.qubes-os.org/ticket/878