Adam Williamson composed on 2014-11-04 23:22 (UTC-0800):
https://bugzilla.redhat.com/show_bug.cgi?id=1123170 , I never have time
to investigate it properly and provide details - sorry about that. But I
guess the same way of thinking would say the timer is a 'step in the
right direction' for me because my system will eventually give up and
hard power off after 30 minutes - but does that really practically make
me feel like I'm getting a better experience?
I've seen shutdown delays on various installations going back to when systemd
was very young. Often they seem to stem from start processes that reported
failure at init time, so at shutdown time, instead of stop jobs, I see
*start* jobs stalling.
One of the easier ways to cause a shutdown delay is to try to CAD right after
making a boot menu selection and realizing I chose the wrong one. That
typically will hang with message failed to store sound card state, and
continually repeat for as long as CAD is held down. It doesn't happen on
every installation, but it is common. Rather than trying to troubleshoot any
of these hangs I invariably have more urgent things to do and reach for the
reset button or power switch.
--
The wise are known for their understanding, and pleasant
words are persuasive. Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
