The mouse appears, but does not work during install, meaning a user must use the tab key and enter, which is not an ideal user experience (seeing something not working, and having to use a keyboard).
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | mak | T132 OEM Install: Mouse and keyboard not working | ||
Resolved | mak | T123 XDG dirs not visible on first boot after fresh OEM install |
Event Timeline
This is related to the keyboard-not-working issue, which is incredibly persistent. We tracked it down to the expat package in Debian, but there seem to be more components involved, making it hard to pin down the issue.
Also, the internet connection being flaky here at Debconf is a problem for rebuilding the debian-installer. I'll do some more tests when I can (new images already exists, but the bug isn't gone yet).
Okay, the initial Debian bug that KiBi fixed was not the one we had in PureOS, but the exact same bug is affecting Debian now.
This issue is highly unstable in when it shows, but is at least reproducible with the same configuration of packages. Cyril is trying for find the cause of the problem by bisecting with Debian snapshots, and I am more randomly poking it to maybe find the cause of this issue.
We know the culprit now. As expected, it's in udev: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872598
That is impossible, since that would mean we need to downgrade our kernel, which we can't (ever) do.
Fortunately, this bug is easy to fix, now that we know the cause.