[Bug 1636503] Re: recovery mode gets borked after some time out
Dimitri John Ledkov
launchpad at surgut.co.uk
Tue Oct 30 14:25:46 UTC 2018
bah
** Also affects: friendly-recovery (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: friendly-recovery (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recovery mode gets borked after some time out
Status in friendly-recovery package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Invalid
Bug description:
(Linux mint 18 / Xenial)
after booting in recovery mode from grub.
If you just wait 30-60seconds, a new stream of messages appear and something gets messed up, you can't use recovery mode any more, you have to do a hard reboot.
You don't need to do something in particular for this to happen,
simply some time out occurs.
-------------------
more precisely, one of the messages say(copied manually):
"[FAILED] Failed to start Console System on Startup logging.
see 'systemctl status console-kit-log-system-start.service' for more details.
It seams, it tries to launch a second recovery mode on top of the
previous one after the error.
------------------------
I confirm, this is happening on both my PC linux mint 18 64bits,
laptop linux mint 18 32bits and some one else from a forum on a
ThinkPad X201 with Mint 18 KDE 64-bit.
On my systems, both are fully up to date, 32 and 64 bit. Kernels don't
seam to change anything.
systemd version 229-4ubuntu11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1636503/+subscriptions
More information about the foundations-bugs
mailing list