please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I had the same issue, too...
Lots of messages saying "Timed out stoppping ...".
The system never rebooted.
Here is what fixed the problem for me:
Firstly, I activated systemd's debug shell using 'systemctl enable
debug-shell.service'.
Then I initiated a reboot and when the problem occured, I
In my case the LUKS stuff was unrelated and I was experiencing shutdown
hangs because I had daemonizing processes started by /etc/rc.local:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1656237
I managed to discover that by pre-killing a bunch of processes before
shutting down, which
I have this problem on a system, and it *never* finishes stopping. It
prints out a bunch of "timeout" messages about stopping various disks,
then hangs forever stopping the crypt disk. I'll try to get an image of
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm resetting these to Confirmed since it looks to me like Amir may have
accidentally set them to incorrect statuses.
Thanks
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
--
You
I'm curious about these two status changes:
Changed in systemd (Ubuntu):
status: Confirmed → Fix Released
Changed in initramfs-tools (Ubuntu):
status: Confirmed → Fix Committed
Would it be possible to have pointers to the commit(s) that fixed this?
Thanks!
--
You received this
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reboots now hang indefinitely with the laptop user. Any update on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554795
Title:
timeout on restart or shutdown with LUKS root
To manage
Are there any workarounds for this for already installed Ubuntu
installs?
I have a laptop user that is having 3+ minute shutdowns for this LUKS
timeout issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554795
Title:
I'm going to open a seperate ticket for the typo/cosmetic issues noted,
so that this ticket can focus on the core. I'll note the ticket number
here once I've created it, which I'll do on the other side of my
commute.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1554795
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (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/1554795
In addition to the typo, there may be an issue where the new setting I
poked in is used, but the hardcoded default is still displayed on-
screen. I've not been able to capture this on camera as yet, and I have
yet to set things up such that all the generated messages are stored for
later perusal,
On Sun, Mar 20, 2016 at 08:09:56AM -, Mason Loring Bliss wrote:
> I just managed to time it right such that I caught the error on my
> screen, and in doing to noticed a glaring typo that's likely indicative
> of the overall code quality of the related software.
The typo looks like an easy
I just confirmed that I see this on a laptop as well. Conveniently, the
laptop install is not using MD-RAID or ZFS - it's using LVM on LUKS on a
single disk, so it's a simpler case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Assuming this isn't fixed any time soon, I'm running with this:
mason@ogre /home/mason$ cat /etc/systemd/system.conf.d/expletive.conf
# required singleton - high ceremony
[Manager]
#DefaultTimeoutStartSec=15s
DefaultTimeoutStopSec=15s
Note that while "Manager" is evidently the only possible
I just managed to time it right such that I caught the error on my
screen, and in doing to noticed a glaring typo that's likely indicative
of the overall code quality of the related software.
I'd be grateful for debugging tips. I hope Canonical's not going to ship
software that punishes LUKS
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554795
Title:
timeout on restart or shutdown with LUKS root
To
19 matches
Mail list logo
