-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
qrexec-daemon writes log to /run/qubes/ instead of /var/log/qubes/ #9185
Comments
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
How to file a helpful issue
Qubes OS release
R4.2
Brief summary
As in the title
Steps to reproduce
Expected behavior
Log written to
/var/log/qubes/VMNAME.log
Actual behavior
Log written to
/run/qubes/VMNAME.log
Looks to be a regression caused by 2901f001fe8f1bc7529d742b3ccf6c2b24811d7a
The text was updated successfully, but these errors were encountered: