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"No policy definition found for qubes.InputKeyboard action" on resume from suspend #3168
Comments
andrewdavidwong
added
bug
C: core
labels
Oct 12, 2017
andrewdavidwong
added this to the Release 3.2 updates milestone
Oct 12, 2017
mvermaes
referenced this issue
Feb 27, 2018
Open
qubes.InputKeyboard prompt when resuming from sleep, but no external devices attached #3636
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
vincentadultman commentedOct 11, 2017
Qubes OS version: 3.2
Steps to reproduce the behavior:
Suspend laptop, resume laptop.
Expected behavior:
I am not (knowingly) trying to pass a device, so expect no policy window to appear.
Actual behavior:
Message box appears in dom0 after resume from suspend with text
Title = "[Dom0] Add a new entry"
Text = "No policy definition found for qubes.InputKeyboard action. Type YES if you want to create a default policy file"
Buttons = Cancel & Okay
General notes:
This occurs on laptop I have been using since 3.0 with internal keyboard and trackpad/point. Perhaps after switching usbvm to fedora25 template from fedora24? In any case there is no keyboard device attached to the usbvm (which has all system usb controllers and devices, inc built in webcam and fingerprint reader).
Having never tried to use the Qubes input proxy, I've not got input-proxy-receiver package installed in dom0, so don't know if this message is expected in some fashion (seems not, as I'm not trying to pass keyboard actions from any vm into dom0...at least intentionally...). System has been upgraded in place from 3.1 and I have tasket's vmauth file in place in /etc/qubes-rpc/policy/ to use with dispvms but have not otherwise touched the default policy files.