Bug 24468

Summary:	M7 in a Vbox client, loses connection to keyboard
Product:	Mageia	Reporter:	William Kenney <wilcal.int>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	NEW ---	QA Contact:
Severity:	minor
Priority:	Low	CC:	marci_r, marja11
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	journalctl - lost keyboard connection

Description William Kenney 2019-03-05 22:06:45 CET

Description of problem:

X86_64 Plasma

Only in a Vbox client. After install initially both the Keyboard and Mouse work
just fine. Sometimes, in a few minutes, the keyboard no longer responds while
the mouse still works. Situation occurs with both a wired and wireless USB
keyboard and mouse. Have not seen the situation on real hardware.

Only way out is to force reboot the Vbox client.

Hold action on this until M7 Beta 2 Release 3 Live media is released.

Comment 1 Marja Van Waes 2019-03-06 07:22:04 CET

When that happens again then, after force-rebooting it, before it happens again, can you please run


    journalctl -ab -1 > log.txt


and attach log.txt to this bug report

Note the "-1" in that command, that is important to get the logs of the _previous_ boot.

CC: (none) => marja11
Assignee: bugsquad => tmb
Keywords: (none) => NEEDINFO

Comment 2 William Kenney 2019-03-06 20:16:14 CET

Created attachment 10844 [details]
journalctl - lost keyboard connection

Somewhere around Mar 06 11:01:01 is when I lost connection with the keyboard.
Mouse continued to work properly.
Some pretty ugly errors around 11:01:39

Comment 3 William Kenney 2019-03-06 20:20:41 CET

The first time I noticed it was when I opened a terminal and the keyboard
would not put text in the terminal.

Marcel Raad 2019-03-21 22:08:10 CET

CC: (none) => marci_r

Comment 4 William Kenney 2019-05-17 22:11:13 CEST

This is still an issue.
It is not a release blocker
I have found that once booting into the client and having no keyboard response
or losing keyboard by simply completely getting out of the client and back in
the problem goes away. Sometimes perminately, sometimes not.
Setting Priority to "Low" and Severity to "Minor"

Priority: Normal => Low
Severity: normal => minor