console-conf says "device managed without user" when device definitely has a user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
From the version of console-conf included in core18 20210722 (revision 2127 for arm64 installed on a Raspberry Pi 4 with Ubuntu Core 18), I definitely setup the device via console-conf initially, then had some issues with some failed kernel refreshes due to the DTB fix debacle, and now when I finally have restored my device after a series of failed reboots and such, console-conf thinks my device is "managed without user" when I definitely have a user.
And more confusingly when I refresh snapd while console-conf is running, then there is a fault that triggers console-conf to think it should run again (which it should not since there is already a user), so to see what it tries I triggered it and after hitting "Done" on the network config page, it crashed with the following output and went back to displaying "device managed without user". See
https:/