We have a Raspberry Pi 2 Model B using Raspbian installed from/on NOOBS card. The GUI desktop was fully functional for several days.
While trying to get Python picamera module to work, decided to do: sudo apt-get upgrade This was the first time we had done that.
Now the system boots to the GUI desktop, but at the desktop, the keyboard and mouse do not respond.
If I press Shift immediately after power-up, I can get into the NOOBS pre-boot screen. On that screen the keyboard and mouse work just fine. If I let it begin booting Raspbian I can pause and resume the boot process (pause and resume message display) using Ctrl-S and Ctrl-Q.
Notable messages include: Ones from usb 1-1.2 and usb 1-1.3 reporting that it detected the mouse and the keyboard as new USB devices, apparently without issue. Then, just after "[info] Loading kernel module snd-bcm2835.", I get:
libkmod: ERROR ../libkmod/libkmod.c 554: kmod_search_moddep: could not open moddep file '/lib/modules/3.18.5-v7+/modules.dep.bin'
later I get:
[....] Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory
and another instance of the same "Error opening '/dev/input/event*'..." a few lines later, after entering runlevel 2.
Do the messages relating to /dev/input/event* indicate why the keyboard and mouse don't respond in the GUI?
Why would they respond prior to launching the GUI?
Is it possible or likely that the earlier "kmod" issue is related to the subsequent keyboard/mouse problem? What might the resolution for that be? (What is a moddep file?)
If fixing this requires interacting with the system, how can I prevent the system from launching the GUI on boot?