Comment 9 for bug 1706939

Revision history for this message
Doug McMahon (mc3man) wrote : Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

Yep, this is really messy..
Did 7 boot ups > restarts & got 4 different results

Twice got normal restarts that also included the pop up about 'remove media, press enter'
Twice got no pop up but the shutdown was text based & 'hung' on no particular errors, ctrl+c set it going again to a completed shutdown
Twice got the 'A start job is running for Hold' hang
Once got the 'Wait for Network` hang (- only session where I enabled wifi..

The systemd timeout ones are the most egregious as they're no limit.
Worst case scenario, is there any way to set all live session start/stop job's to a limited timeout? (30 sec or so max