Hide Forgot
Description of problem: Summary say it all. Version-Release number of selected component (if applicable): gnome-power-manager-2.28.3-5.el6 How reproducible: 100% Steps to Reproduce: 1. put (on the beginning) exit 1 to /usr/sbin/pm-hibernate or simply rename /usr/sbin/pm-hibernate 2. System-Shut Down..-Hibernate 3. Actual results: No notifications about wrong exit status of pm-hibernate script Expected results: g-p-m should notify user about errors durring suspend/gibernation Additional info: No regression rhel6 also show any notifications.
Not sure but could be related to https://bugzilla.redhat.com/show_bug.cgi?id=640296.
AFAIK this looks like two problems: 1) The DeviceKit-power doesn't checks pm-hibernate exit codes. It is also the same with upower in Fedora (bug #689034). But to be fair the pm-utils in RHEL-6 doesn't catch the hibernation errors from kernel, thus the current state of DeviceKit-power is probably OK. Thus for error simulation you need to rename or remove the /usr/sbin/pm-hibernate. 2) It seems that you used the gnome-session command for hibernation, but it seems that the gnome-session doesn't implement the UI failure notifications (there are only glib debug warnings). In order to use gnome-power-manager for hibernation you have to enable the GPM hibernation command by: gconftool-2 -s /apps/gnome-power-manager/ui/show_actions_in_menu -t bool true and then activate this command from the menu that can be opened by right clicking on the GPM battery tray icon (icon must be enabled or can be seen while on battery). Thus reassigning to gnome-session, because the UI failure notification should be added there.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. 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. If you would like it considered as an exception in the current release, please ask your support representative.
Since RHEL 6.2 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.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/