-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Global Config: Unexpected policy file contents
message at top of USB Devices window
#9433
Comments
It would be helpful if we could see what is below the red box. The screen snapshot does not show that. |
Why would that be helpful? I excluded it because I thought it was irrelevant. |
GUI Widgets are usually in order (from left to right, top to bottom). Having a clue on the failing widget should allow easier troubleshooting while inspecting the Glade files. It should be something like this: I would like to know what is failing there. The USB Qube query or the 3 drop-down menus down. I suspect the former. But I want to be sure. |
I think you might be right. Another reason I didn't want to include this portion is because my USB qube name is not
|
I think this is the key information. Yet the rules are about IMO in this situation (expected set of input-proxy rules for no longer existing USB qube) the message should be different, like "found rules for not existing USB qube, they will be removed when saving changes on this tab", or something like this. @marmarta what do you think? |
I believe I have a clear idea on what is happening here. The errors belong to |
I don't think we should ignore policies completely - but I think the approach with "this contains policies for a non-existent qube" is better. Not sure if we should discard them completely... there could be some interaction with backup/restore that leads to unexpected configuration loss here? Also, it would be nice to have a single place in the system to define which one is a sys-usb (I know we can't, but a girl can dream, right?) |
This might be doable. The same mechanism that detects PCI USB Controllers and attaches them to the stock |
This is more or less what the global config already does to list USB qubes on this screen. It does with multiple of them too (for example I have one per controller on one of my system and it works just fine). |
Yeah, but I'd like for things to magically happen when a user connects a USB controller to a qube. Automatically - or with a question - modified policies etc. But I think this could open problems in edge cases. |
How to file a helpful issue
Qubes OS release
4.2
Brief summary
When I open Qubes OS Global Config and select USB Devices on the left, there's a red box at the top with a message about
Unexpected policy file contents
.Steps to reproduce
Expected behavior
No warnings or errors about unexpected policy file contents (or an explanation of what the problem is and what, if anything, should be done about it).
Actual behavior
Text version:
Commentary
It's not obvious to me where these rules came from or what's wrong with them.
Let's try a grep:
Okay, it looks like
qubes.InputTablet
is present in only one place:50-config-input.policy
. This appears to be a default policy file that was created by Qubes OS. As far as I know, I've never touched this file. I put all of my custom rules in30-user.policy
. I also don't have anyqubes.InputTablet
rules of my own, or else they would've shown up in the grep results.The text was updated successfully, but these errors were encountered: