Hide Forgot
Description of problem: In gnome, run system, administration, software update. Updates are downloaded, tested then installed. Click on system, shutdown, "shutdown|log-off|hibernate|suspend" Machine is allowed to be "shutdown", it should not be. As a result when restarted the machine can be left in a state which renders it inoperable. A user should be warned that updates are being installed, and the "shutdown" process canceled.
Additionally, same can be said of pressing fn-f4 or fn-f12 machine can suspend/hibernate while updates are being applied.
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Shutting down while updates are being installed is a sure fire way to wreck a system. Dozens of employees have very quickly bricked their machines. I'm shocked that Gnome hasn't resolved this issue already with a set of warnings and methods to halt the shutdown process before getting into a unrecoverable state. We've implemented several pre-Shutdown notification warnings to inform the user of background patch installation and that KVM virtual machines are still running. Disappointed that we won't get a fix for a major deficiency.
Marking as a duplicate. The fix suggested in #669798 is not ideal, but may act as a stop gap. It basically inhibits suspend and hibernate during a transaction, also stop the active user from logging out or shutting down. This only works for the active user and the user is also able to still shutdown using tools on the command line. The active user will be warned if they try to shutdown only using the GNOME graphical desktop. A better fix will be available in RHEL 7 where systemd can be used to inhibit shutdown systematically. *** This bug has been marked as a duplicate of bug 669798 ***
Outstanding. Thank you!