Keyboard stop suddenly, how to revoke the input server?

I am not sure what is triggering the keyboard to just stop working!
Keyboard and Keypad! Suspicious programs are Telegram/IceWeasel and, or TeamMonitor!

Mouse is auto restored, but no way to stop and run the input server to make the keyboard work with mouse only!

I use HAIKU on 64bit nightly on a HP-Pavilion.

Any idea how to restart the InputServer with mouse only?
Of course, best would be if InputServer would start automatically after stopping the team, just like the Deskbar or Tracker and the mouse!

I didn’t test it but I think an app like ScreenKeyboard would help with that so you can use a virtual keyboard if that happens… although maybe the issue you’re facing would block this app from working as well?

Why don’t you look for a matching bug report or submit a bug report?

Is it a bug or is it just not enabled or correct handled?
It is clear the input_server should autoload after stopping the thread!

It would be handy for situations like this to have something like log_server, so dev could see OS output during run. See Console in macOS/GNUstep.

open terminal

type tail -f /var/log/syslog

There you have the output during run!

If you don’t have a working keyboard you can copy paste that command, or if you’re really desperate you can drag and drop characters from keymap preferences or character map into Terminal.

The keyboard is not working. How would that not be a bug?

1 Like

Using tail -f /var/log/syslog
I cannot get this bug triggered atm!

Physically unplug and plug keyboard again may help.

I sometimes experience problem that keyboard do not work after boot, but can be fixed by replugging.

No it is a laptop/notebook!
But I will try a USB-keyboard next time I trigger this bug to see if the keyboard will initialise itself!

EDIT: Plugging in an external USB-Keyboard does work!

And yes turning on power saving mode makes the laptop/notebook keyboard not respond! So looks like duplicate of #19477, hope it helps!