Control: affects -1 xorg Control: severity -1 grave Severity: grave Justification: renders package unusable
Thanks, I also figured this out myself separately by running `libinput debug-events`, hopefully this helps someone else stumbling upon this strange behaviour in the future. However I am still confused to on how I managed to fix it. On one machine (the AMDGPU one) `libinput debug-events --verbose` would complain about certain devices not being initialised by udev, including the keyboard device. Upgrading udev from version 243-5 to 243-7 and reloading udev by running `udevadm control --reload-rules && udevadm trigger` and then restarting lightdm worked. Perhaps this bug is related to #944586? Then again, on the other machine (Intel graphics) it was sufficient to simply run `libinput debug-events --device $device`. Oh and another thing for people wanting to play around with this, when you run `systemctl disable lightdm` and then fix the problem and then run `systemctl enable lightdm` the latter does not work for some stupid reason, even though the former command worked. You have to run `dpkg-reconfigure lightdm` to make it work again. X Sven Joachim: > Control: reassign -1 udev 243-5 > Control: forcemerge 944675 -1 > > On 2019-11-16 03:45 +0000, Ximin Luo wrote: > >> Package: xorg >> Version: 1:7.7+20 >> Severity: important >> >> Dear Maintainer, >> >> After upgrading a bunch of packages on two very different machines, X no >> longer >> responds to keyboard or mouse input. >> >> I am using lightdm with XFCE, the problem is present both in the lightdm >> login >> menu and also in XFCE when using `startx` directly. >> >> Nothing obvious is in the kernel or system logs or Xorg.0.log. > > That seems to be bug #944675 in udev. > > Cheers, > Sven > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
