*** This bug is a duplicate of bug 1662137 ***
https://bugs.launchpad.net/bugs/1662137
** This bug has been marked a duplicate of bug 1662137
16.04 recovery shell works only for two minutes
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a mem
I can confirm, that for 18.04 32/64bit it's gone.
I don't know for 16.04 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recovery mode gets borked after some time out
To manage notif
nothing to do with systemd, purely a friendly-recovery induced issue
which should have been fixed across all stable releases now. Please
retest, if this is still a problem for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
please retest with 229-4ubuntu21.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recovery mode gets borked after some time out
To manage notifications about this bug go to:
https://
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 mem
wait a minute, it doesn't ask the root password
That's rather bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recovery mode gets borked after some time out
To manage notificati
It looks like it is an error with the terminal display. I can still
type and get commands to go through, but the display is garbled spacing.
I can call nano /etc/fstab and get my fstab file without issue.
Everything is properly spaced and I can type without issue.
--
You received this bug notifi
Confirmed – mostly.
Running: Mint 18 Cinnamon 64-bit
Kernel: 4.4.0-78
Laptop: Lenovo Thinkpad Yoga 12
Backstory:
I have a dual boot with windows 10, which I evidently messed up because I would
get a (busybox) prompt every once in a while. Generally running a manual fsck
would fix that. Last n
Can confirm, this bug affects me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recovery mode gets borked after some time out
To manage notifications about this bug go to:
https://bu
I experience the same issue as OP after a clean install of Ubuntu 16.04
4.4.0-72.
Nothing can be done in recovery mode that takes longer than one minute,
otherwise some timeout fires, console spews several screens of messages
indicating processes being stopped, and it loops back into the recovery
still borked with systemd 229-4ubuntu13(xenial)
-_- guys, isn't this a serious bug?
You are left with unusable recovery mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recover
affects my PC, laptop and some one else.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recovery mode gets borked after
12 matches
Mail list logo