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

Lenovo W520 fujitsu siemens e5730 /usr/bin/qvm-start sys-firewall failed #3987

Closed
jsmgithub opened this Issue Jun 13, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@jsmgithub

jsmgithub commented Jun 13, 2018

Qubes OS version: 4.0

Affected component(s):


Steps to reproduce the behavior:

Expected behavior:

Actual behavior: I hope that will be fixed.

General notes:


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jun 14, 2018

Member

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

Member

andrewdavidwong commented Jun 14, 2018

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

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