Keyboard and mouse completely unresponsive after pkg upgrade and reboot

M

Matthew45

I'm running FreeBSD 15.1-RELEASE with KDE Plasma 6.7.5, SDDM and NVIDIA drivers.

Today, October 18, I performed a normal sudo pkg upgrade, which included the following updates:
  • sddm: 0.21.0.36_6 → 0.21.0.36_7
  • plasma6-kdeplasma-addons: 6.7.5 → 6.7.5_1
  • plasma6-union: 6.7.5 → 6.7.5_1
After the upgrade completed, I performed a normal sudo reboot.

FreeBSD booted into the graphical desktop, but my keyboard and mouse were completely unresponsive. The mouse pointer was also missing.
I couldn't open Konsole, interact with KDE Plasma, or switch to a TTY using Ctrl+Alt+F2.
The only available recovery method was pressing the physical Reset button on my computer case.
After this hardware reset, both the keyboard and mouse worked normally again. I subsequently performed another sudo reboot, and the system started normally with both input devices functioning.

Additional checks:
  • zpool status: ONLINE, zero errors.
  • sudo pkg check -d: Completed without errors.
Hardware:
  • ASRock H97 Pro4 motherboard
  • Intel Core i7-4790S
  • NVIDIA GeForce RTX 2060
  • USB keyboard and mouse
Has anyone experienced a similar issue after recent SDDM or KDE package updates? Could this be a USB initialization issue or a problem with the graphical session?

The issue has not recurred so far. I just hope my system is fine, because i red somewhere that hard reset via phisical button can damage system..but i had no other option..
 
xf86-input-libinput is correctly installed version 1.5.0..

[ 17.809] (--) Log file renamed from "/var/log/Xorg.pid-2692.log" to "/var/log/Xorg.0.log"
[ 17.810]
X.Org X Server 1.21.1.25
X Protocol Version 11, Revision 0
[ 17.810] Current Operating System: FreeBSD FreeBSD 15.1-RELEASE-p5 FreeBSD 15.1-RELEASE-p
5 releng/15.1-n283639-893c7c99b60d GENERIC amd64
[ 17.810]
[ 17.810] Current version of pixman: 0.46.4
[ 17.810] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 17.810] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 17.811] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 18 20:21:07 2026
[ 17.811] (==) Using config directory: "/usr/local/etc/X11/xorg.conf.d"
[ 17.811] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
[ 17.812] (==) No Layout section. Using the first Screen section.
[ 17.812] (==) No screen section available. Using defaults.
[ 17.812] (**) |-->Screen "Default Screen Section" (0)
[ 17.812] (**) | |-->Monitor "<default monitor>"
[ 17.812] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 17.812] (**) | |-->Device "Card0"
[ 17.812] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
/var/log/Xorg.0.log
 
This happened to me once, and it was a faulty (or too long) USB cable. It worked before, then when I tried it on some systems it worked but on others. My guess was there was noise on the wire, and this caused device detection to time out on some systems. I never looked into it properly, since replacing the cable was an instant fix. But it was a real puzzle for a while.
 
You must log in or register to reply here.
Back
Top