On Fr, 2016-08-26 at 12:44 +0000, Mathieu Trudel-Lapierre wrote: > I don't know why you're seeing the PID persist, clearly something > unexpected happened, but console-conf is meant to be forced onto the > user if the system isn't otherwise coming pre-configured with a user. > It > should not be killed, as that would get one a system that is unusable > (with no user to login to). > > I'm inclined to mark this Won't Fix. We can certainly discuss this > further. > > ** Changed in: subiquity (Ubuntu) > Status: New => Won't Fix > well, this is a properly configured system with ubuntu user and wlan0 device already that i use for development (like many others that use our images). after todays ubuntu-core auto-update it could not boot properly anymore and showed this behaviour. seemingly console-conf did not detect that there is a user and a wlan0 device.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617251 Title: console-conf unkillable To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1617251/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
