Seems I did, however do not recall. I know I miss-spelt the directory once but not sure how this was created. Seems to contain nothing tho, so will delete it as there is a similar directory but that one has been rendered useless hence the replace 80-whonix policy directory.
Not certain how this would cause any issue tho as contain nothing. Not confident that this is the cause.
Should I attempt to reboot anything now?
Try to restart the service:
sudo systemctl restart qubes-qrexec-policy-daemon
Then check the service log again:
journalctl -b -u qubes-qrexec-policy-daemon
Maybe youâll need to reboot the system.
Its working now. Logs giving no error.
Thanks boss. Your the best!
Any idea why such a minor thing wouldâve stopped all operations?
A fail safe when errors occur or not as defined route to execute i.e the execution process might not be as fine designed so easier mitigation is to prevent all when minor conflict occurs instead of a bypass or self resolution mechanism?
The policy files are read one by one and if an error in syntax will be encountered then itâll crash and stop the further reading.
Itâs better to use the Qubes Policy Editor GUI tool to edit the policies because itâll check the syntax before allowing you to save the file to prevent this issue.
Noted. Much appreciated. However maybe some improvement to these checks and process of execution to perhaps self resolve/bypass can one day be implemented. As I would assume this process method is more broad in how the OS operates.
Not sure if there is a more visible method on alerting user of these kind of unknown conflicts, but might be something cool to have an admin panel like this in a easy use GUI form.
Idk just a fun thought. Maybe it will get suggested/implemented in the future just so certain functions are more robust and user friendly which I think is one of teams/community goal to expand adoption.
This is going to be tricky to fix. In the future there will be an API to alter qrexec policy, which will only allow the creation of valid policies.
Right now, a single broken policy file results in all RPC calls being ârefusedâ which is a bit misleading.
Intentional behavior.
1 Like
Yea Iâve read alot of great proposals and good points in issues brought up in forums, etc. Especially when looking at support guides and discussions.
Like the Qubeslive/cloud feature that was discussed and mentioned a big while back.
I could probably find it but is there any form of progress/roadmap page on these things.
Ik that Qubes is ofc a small team, with community contributors but I have been very interested in seeing the direction and âwhat to expect updatesâ which I would like to be more updated on for myself. Again I have not taken the time to actively look but sure there is. Any links is appreciated however will be looking soon, certain it would be quick to come across by(like the forum & the official github page, news docs, etc). Minaly anything you think my be really interesting and exciting to monitor, cause ofc ik there is a status board but am curious.
I think there is no roadmap or anything like that.
You can check the issues that developers are currently working on by filtering the open issues on github by assignee e.g.:
is:open assignee:DemiMarie