Closed makergamer closed 6 months ago
Thanks for finding this!
I did find that dpkg-reconfigure keyboard-configuration
opens a whiptail menu if a USB keyboard is attached. Do you by chance also have one attached?
(Also figuring out how to disable the menu)
Ooo. that's a possibility. It's been a few days and just left on-call so I cannot be for sure given my fried memory.
I have attached a micro keyboard dongle as needed for things I haven't learned the chord/overlay combos for. So there's a real possibility a "usb keyboard" could have been attached, if the dongle was plugged in, even if I didn't have the real keyboard powered on & using it.
Is there an option for the make file to flag for non-interactive/headless mode as to skip the dpkg-reconfigure keyboard-configuration
?
I can imaging the interactive appearing if another kind of HID device is plugged in - like a retro controller that maps to keys, etc.
I could always do updates using an ssh+tmux session (and double check the dongle is not connected).
Figured out that setting DEBIAN_FRONTEND=noninteractive
before the Makefile runs dpkg-reconfigure keyboard-configuration
will fix this issue. I've updated the beepy-kbd
repo and packages to automatically apply this when building the module.
Trying out the new v1.0-rc on my Beepy+RPIZero2W. Like always, immediately after getting on the network, I issue an 'apt update && apt upgrade'. Once it reaches the DKMS portion, it drags on for evah:
I've seen this kind of thing before. I bet it is some interactive thing like
whiptail
ordialog
. Yup.I had to kill this process to resume as killing
whiptail
wasn't enough:but then repeat the kill for every image it was trying to build, and clean up the orphaned
whiptail
processes.