System: Slackware64-current.

Just updated via slackpkg, and noticed in the changelog that evdev is being replaced by libinput. Installed both libinput files, and following a reboot found myself locked out - keyboard and mouse (USB) totally unresponsive!

Luckily, I managed to SSH in from another machine and remove both libinput packages. This restored normal operation. If I hadn't had another machine, I could have been in trouble!

I assume some extra configuration is necessary to use libinput, but this isn't clear from the changelog, so be careful!

I've emailed Pat...

--
Pete

I had the exact problem, it turns out the newer official "libinput" package did actually not install because there is an existing one at Aliens current-repository (http://bear.alienbase.nl/mirrors/peo...6_64/libinput/: libinput-1.3.x-alien. Because alien-repository is prioritized over slackware64, it did not upgrade to libinput-1.5.x.

So, if that is the problem temporarily disable aliens repository to fully upgrade.

Nowadays you can login from your phone too (if that was smart enough...)

No, I don't have the Alien repository enabled on that machine - its pure Slackware. Good thought, though! As is the 'phone suggestion, though I didn't know you could get a terminal window up on that! ;-)

--
Pete

I've installed libinput yesterday and haven't noticed any changes (except that /var/log/Xorg.0.log clearly shows that libinput is in use), all input devices working as expected.

Actually, there are three new packages:

Maybe you forgot to install one of them?

2 members found this post helpful.

Ah! Perhaps I missed libwacom! I assumed that was only needed for pen & tablet devices!

Good spot! I'll give it a try....

--
Pete

Yes! That was it! My fault, and well spotted!

--
Pete

I don't know about iOS, but if you have Android, by far, the best SSH client I've used is JuiceSSH. It has the most intuitive interface (a special pop-up keyboard providing you common things like the pipe symbol, forward slash, tab, ctrl, etc), allows code "snippets" enabling you to save commands, and allows you to store multiple machines with multiple users. It even supports ssh keys if you don't allow username/password logins.

The code snippets might require the pro version, but so far, I've used it to log into my machines almost 700 times, so I paid the few bucks to get the pro version. I don't remember what features require the pro version, but it's still plenty functional without it (I used the free version for at least a year before getting pro).

I've got another thread going on this same issue. I thought the problem might be conflict with libinput-1.3.3-x86_64-1alien and libinput-1.5.4-x86_64 in relation to libwacom or xf-86-input-libinput. I have libwacom installed and I was still totally locked out under X, requiring a reboot to recover CLI.

I did run the slackpkg install-new for libinput and libwacom, but the slackpkgplus priorities made alien's package of earlier version the priority. In checking he X.orgO.log I see that it is searching and can't find LIBINPUT_1.5. It attempts this libinput load about five times and then stops WITHOUT falling back to evdev!

I've run in to this problem before and sometimes you have to rename slackpkgplus.conf so regular slackpkg loads latest from Pat's repository.

Bassmadrigal: Thanks for the tip. That's certainly something I shall investigate!

Dugan & Bamunds: My other machine does have the Alien repository enabled (I have KDE 5 on it) and as suggested, this does stop libinput-1.5 from installing - UNLESS you disable slackpkg+ (there is an on/off switch in the conf file).

On the first machine it was entirely my fault, as I hadn't read the changelog closely enough. I'd passed over libwacom as I don't have a wacom (or similar) tablet, and never needed it before. By the time I updated the other machine, I had already read bamunds post about the Alien repository and managed to side-step the problem, but if it hadn't been for that, I would have certainly fallen for that "gotcha"!

--
Pete

I was lazy and got bit by that libinput slackpkg+ issue as well. Luckily, I was able to burn a current64 dvd from the terminal and re-install. The only thing I had to redo was installing plasma 5 kde. So far everything is working normally again. Going back to doing all updates by hand so I make sure things get installed in the proper order.

This issue also covered in this thread http://www.linuxquestions.org/questi...ut-4175597831/. It seems that depending on how you have slackpkg+ setup you may or maynot get the latest libinput installed. It would be beneficial for any user after installing updates to always verify that all updates have installed before rebooting.