Closed grahamperrin closed 7 years ago
Not limited to KDE; symptoms here are also reproduced following every log out from Lumina. Most remarkable:
The tab key is not a workaround.
No visible response, at the indicator within the keyboard, to keying Caps Lock. It's as if truly, the keyboard is not driven in good time.
I wonder whether we have two separate issues here.
Not released yet. Not even pushed to UNSTABLE.
Understood, thanks … and more recently reproduced with trueos-desktop-201701042114 on FreeBSD 12.0-CURRENT #12 5ef9376(drm-next-4.7): Thu Dec 29 16:26:36 …
Reopening after push to unstable
Posted to wrong ticket the first time. Ignore deleted message.
I wonder whether we have two separate issues here.
We probably do.
Keyboard on USB apparently not driven in good time at startup, …
First impressions of trueos-desktop-201701060022 on FreeBSD 12.0-CURRENT #13 42158f1(drm-next-4.7): Thu Jan 5 22:37:19 UTC 2017 root@gauntlet:/usr/obj/usr/src/sys/GENERIC
:
– I'll continue to test. If reproducible, I should probably create a separate issue.
Keyboard on USB … only partially usable when the display manager reappears after log out
… and when the manager first appears.
Early impressions of trueos-desktop-201701060022 on FreeBSD 12.0-CURRENT #13 42158f1(drm-next-4.7): Thu Jan 5 22:37:19 UTC 2017 root@gauntlet:/usr/obj/usr/src/sys/GENERIC
:
Most easily reproducible wherever the manager lists two or more users:
With the change of title of this issue (reduction from two issues, one of which was transient, to one):
The workaround (Tab) is trivially easy when known, but not intuitive when unknown.
If this issue creeps into STABLE then some customers may be frustrated by the sense of falling at the first hurdle. No response to Return or Enter, when a user's name is selected, feels like an obstacle.
This seems to be fixed. Please, in which repo might I find the commit?
From a boot of the fixed environment:
$ about
______ ____ _____
/_ __/______ _____ / __ \/ ___/
/ / / ___/ / / / _ \ / / / /\__ \
/ / / / / /_/ / __/ / /_/ /___/ /
/_/ /_/ \__,_/\___/ \____//____/
General info:
Host:...............momh167-gjp4-hpelitebook850g2-trueos.university.brighton.ac.uk
User:...............grahamperrin
Uptime:.............8 mins
FreeBSD kernel ver:.12.0-CURRENT
FreeBSD world ver:..12.0-CURRENT
FreeBSD git branch:.drm-next
FreeBSD git rev:....3dbce2a
TrueOS ver:.........TrueOS-Desktop-201701261715
Arch:...............amd64
Kernel ident:.......GENERIC
Bootloader:.........BSD
Bootloader type:....EFI
CPU:................Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
CPU cores:..........4
Memory (free/avail):13529 / 16384 Mb
Package set:........CUSTOM
Desktop environment:Lumina
X11 Driver:.........modesetting_drv.so
OSS Driver:.........pcm1: <Realtek (0x0280) (Analog 2.0+HP/2.0)> (play/rec) default
WIFI Driver:........iwm0
$
This issue became most noticeable after I preferred
autoboot_delay="15"
in/boot/loader.conf
and it feels regressive.At the FreeBSD loader: around the end of the fifteen second countdown, when it reaches '2', the keyboard is (still) not driven.
Also after my most recent log out from KDE, there was (if I'm not mistaken) a remarkable delay – at the display manager – before the OS responded properly to the keyboard.
I suspect that the problem began after an update from
5ef9376
to5ef9376
(an update, but no change to the commit reference).Environment
pciconf -lv.txt