Hi all, I updated to the new Titan version of EOS, and now when I get to the login screen, my mouse and keyboard are unresponsive.
I can use the keyboard to navigate the GNU GRUB menu (10+ year old hardware) and select fallback initramfs, but still can’t login. I can access a terminal in the Grub menu, but that’s about all I can do.
Do I need to re-flash the ISO and start from scratch, or is this mend-able?
Thanks!
I too, have this issue.
Modern hardware. Worked just fine before I updated today, used my computer first before updating. Mouse and keyboard unresponsive after update, typing this on work laptop.
Mouse and keyboard both get power (lights on) and work in boot menu. Spare mice and keyboards don’t work either.
I expected to ‘solve’ such issues through the fallback option, assuming it would roll back the update or booted the previous version but alas (now I don’t know what it’s for).
Hi edgeos,
Do you have a laptop or a desktop/workstation? If it’s a desktop, can you unplug and replug the mouse and keyboard to see if that gets it working again?
If it’s a laptop, maybe a Fn key shortcut will help? (Touchpad on/off, etc.)
Yes, first thing I did. It’s a “desktop”.
I also tried different keyboard and different mouse, same issue.
My laptop is affected by this issue, too, since today. But I installed EndeavourOS last year on my laptop.
After today’s last package update which had something to do with the input system (can’t remember the exact package name) I am not able to log into my EndeavourOS installation (KDE) on my laptop because both keyboard and mouse are not responding when trying to type in the KDE password.
Pressing the Fn key does not resolve the behaviour: I cannot detect any F1 to F12 key on my laptop’s internal keyboard which would indicate that it would re-activate the internal keyboard.
Additional info: During the last package update before the issue started to exist as described here in this forum thread, I answered a question in the package update console window. This question referred to a package that, as far as I can remember, could not be updated, and I told the update process in the console window to keep the old version of that package, a package that seems to have to do something with the input system. But I cannot remember the name of that package, its name does not seem to start with the string “input”, because I checked the Web package search on archlinux.org for that.
CC edgeos, HarryTheDutch
Debugging this issue on my machine lead me to lua as the culprit. If you’re still stuck, try adding systemd.unit=rescue.target to your grub/systemd-boot params (if you’re using systemd-boot, you need to press F1 on your boot screen, then e for edit). You’ll boot in a rescue shell. In it you can run:
downgrade lua
and select a version that’s less than 5.5.0
Try if that works for you. Worked for me
EDIT: if you manage to recover using this method, you can probably ensure future updates don’t re-introduce this by first updating lua to latest version, and then explicitly installing lua 5.4.*
# pacman -Sy lua
# pacman -Sy lua54
Ok, tried this. I can edit the boot params and have tried with both fallback initramfs and the default, and neither are opening the “rescue shell”, just proceeds straight to the login screen and keyboard input is still not working….
@ edgeos ,
Here´s a tutorial about how to get into a rescue shell in an EndeavourOS system:
https://discovery.endeavouros.com/system-rescue/how-to-boot-without-a-graphical-environment/2021/03/
When logged into in the rescue shell, execute the “downgrade lua” command and follow all other instructions by @frivolous - except the commands
# pacman -Sy lua
# pacman -Sy lua54
It worked on my machine, and after a reboot, I executed another package upgrade, after that, after another reboot the keyboard and mouse work as expected, so that I am able to login again into my KDE desktop environment.
Why this now works with the latest version of lua? I guess Archlinux provided a fix for lua and the issue which is described here in this forum thread.
@edgeos if you are able to get to the Login Manager, i.e. Display Manager can you shift to a TTY/Virtual console by using the key combination CTRL+ALT+F3 or CTRL+ALT+F4 and then try to log in. What happened in the last update will be available in the /var/log/pacman.log file. That will help you determine the issue at hand.
Thank you for the response. I’m going to try this, this evening when I’m home again and will let know later the result.
I do remember ignoring a Lua install during updating because it couldn’t get a dependency (can’t remember exactly, something with lib in the name but that doesn’t help). I actually made a screenshot of it, never imagining that a Lua issue would mess with my system like it does now.
Lesson learned, will make a photo of errors and warnings next time instead.
It worked, thank you @frivolous and @Phrank !!
It’s asking for a password for root.
It doesn’t show the * which I had it configured to show when typing the password. Is this because it’s in emergency mode?
Only to mention.. there is no such thing as upating to Titan, this is a rolling release …
Titan is only the name of the ISO installer Version.
@ HarryTheDutch, just blindly type and enter the password for user root in order to get into the rescue shell.
Well, I want to make sure that my keyboard doesn’t have a problem as I don’t see any stars and the password I type (which is for my own user with sudo capabilities) is not accepted.
I’m trying that one as I have no idea what other password I have set while normally I’m very meticulous in setting and saving my passwords using a local password manager on another device.
Edit: Got it ! Typing this on endeavour again!
So the warning was ‘cannot resolve “lua54”, a dependency of “libinput”.
Libinput could not be upgraded and it asked whether I wanted to skip package for this upgrade.
As I didn’t read well, I was thinking “what can go wrong by not upgrading lua?” overlooking the libinput part.
I guess I had to break off the whole upgrade.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.