Bug 19322

Summary: Updates killed keyboard and mouse
Product: Mageia Reporter: Alan Secker <alan>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: Normal CC: marja11
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Alan Secker 2016-09-09 17:25:08 CEST
Following today's approx 25 updates, cannot access via keyboard nor mouse.

This MGA 6-sta (or was)
Comment 1 Marja Van Waes 2016-09-09 21:24:19 CEST
Does the mouse work when you see the bootloader screen?

If you have Mga5 installed on the same computer and you can access it, or else using a LiveDVD:

* Please mount the root partition of the install which you updated

* Go to the /var/log/journal/ directory of that root partition

* do, as root, but enter the tab key at the end (so not the enter key!)

  journalctl --since=today -D 

the line will be expanded to something like:

  journalctl --since=today -D 4d8005cdf72d441490233b6e081cd747/

* now you only need to add a space + "> journal.txt" to the line, so you get something like:

  journalctl --since=today -D 4d8005cdf72d441490233b6e081cd747/ > journal.txt

(Of course, if you read this tomorrow, then you need to replace "today" with "yesterday" )
It is now safe to hit "enter"

* And please attach journal.txt to this bug report.

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Component: Backports => RPM Packages

Comment 2 Marja Van Waes 2016-09-09 21:25:14 CEST
s/enter the tab key/press the tab key/
Comment 3 Marja Van Waes 2016-09-10 10:23:37 CEST
@ Alan,

If your mouse and keyboard still work in the bootloader screen, then you could first try to add a space and a 3, so " 3" to the kernel options line, and then press "F10", as explained here:

https://wiki.mageia.org/en/How_to_set_up_kernel_options#With_Grub_2_boot_Loader_2

It is possible that the keyboard still works outside X, or outside the display manager you use. Adding the " 3" should lead you to a prompt where you can login in text mode.

If you succeed to login, then you can become root and run:

    journalctl --since=yesterday > journalctl.txt

After that, please run 

    urpmi --auto-update

to see whether an update fixes the problem.

Please do report back, without your feedback we do not have a clue what may have caused this issue!
Comment 4 Marja Van Waes 2016-09-11 11:38:50 CEST
Hi Alan,

The issue you reported is a very serious issue. Even if no one else reported it yet, this is not something we want to happen to anyone!

I can understand that it takes time to get the requested journalctl.txt file.

Meanwhile, could you please already inform us about at which point your keyboard stops working:

* Can you still enter the BIOS or UEFI right after starting your system?

If so, then:

* Does your keyboard still work in the Bootloader screen?
** If not: which bootloader do you use, the default one, grub2(-efi), or..?
** If the keyboard still works there, then:

* Does your keyboard still work in the login screen of your display manager?
** If not: do you know which display manager you use?
** however, if the keyboard still works, then:

* Can you switch to a VT with, e.g. ctrl+alt+F3 at this point, and login there?
  (to switch back use ctrl+alt+F1)
and
* Which desktop environment do you use?
* If you still cannot use the keyboard and mouse in your desktop environment, does using ctrl+alt+F3 still work, anyway?

Please login to https://bugs.mageia.org/show_bug.cgi?id=19322 to answer, replying to a bugzilla mail is impossible.

Thanks for your help!
Marja
Comment 5 Marja Van Waes 2016-09-11 11:49:03 CEST
Btw, "--since=today" in the command should now be changed into 

   --since=2016-09-09 --until=2016-09-10

(assuming that in your timezone it was September 9th when you hit this problem, if it wasn't, then please change the dates in accordingly)
Comment 6 Marja Van Waes 2016-09-20 18:29:44 CEST
Since there are insufficient details provided in this report for us to investigate the issue further & since we have not received feedback to the information we have requested above & since no one else reported this issue, there is absolutely _nothing_ we can do

Please reopen and attach the requested information, if you hit this issue again in a fully updated cauldron.

Closing as WORKSFORME

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME