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

(internal Notebook) Keyboard not working #2611

Closed
n1LWeb opened this Issue Jan 30, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@n1LWeb

n1LWeb commented Jan 30, 2017

Qubes OS version (e.g., R3.2): R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable): dom0


Expected behavior: Keyboard Working

Actual behavior: Keyboard not working

Steps to reproduce the behavior:

Not sure. Did some template updates in fedora-23 and debian-8 installed a windows HVM which doesn't Autostart

General notes:

The Keyboard is working when entering the disk encryption password. After that the internal Keyboard an the Touchpad aren't working. External mouse and keyboard work. I have no USB VM and didn't tinker with USB/PCI devices.

I started creating a ProxyVM which doesn't autostart, and is not yet used anywhere.

The Keyboard was working until the last full reboot today.

Any ideas?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 30, 2017

Member

This is too localized for qubes-issues. Please consider posting this to the qubes-users mailing list instead. (You can read more about our mailing lists here.)

qubes-users is intended for these sorts of questions and receives much more traffic, which means that your question is more likely to receive a response there.

Member

andrewdavidwong commented Jan 30, 2017

This is too localized for qubes-issues. Please consider posting this to the qubes-users mailing list instead. (You can read more about our mailing lists here.)

qubes-users is intended for these sorts of questions and receives much more traffic, which means that your question is more likely to receive a response there.

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