Bug 1654568
| Summary: | xfsm-shutdown-helper --hibernate fails: Failed to execute child process ?/usr/sbin/pm-hibernate? (No such file or directory) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Milan Kerslager <milan.kerslager> |
| Component: | xfce4-session | Assignee: | Kevin Fenzi <kevin> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 29 | CC: | arjun.is, codonell, dj, fweimer, kevin, law, mfabian, nonamedotc, pfrankli, rjones, rth, siddhesh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-27 22:49:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Milan Kerslager
2018-11-29 06:17:02 UTC
This is most likely an application bug. Please try to capture a coredump and a backtrace with debugging symbols. Thanks. By running the command by hand I managed to see the real error message.
Unfortunately I don't understand what it means - Fedora has no program
called "/usr/sbin/pm-hibernate".
$ pkexec /usr/lib64/xfce4/session/xfsm-shutdown-helper --hibernate
(xfsm-shutdown-helper:31209): GLib-WARNING **: 06:16:00.492: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Failed to execute child process ?/usr/sbin/pm-hibernate? (No such file or directory)
Segmentation fault (core dumped)
The stack trace is consequently useless:
#0 0x00007f5f4873b610 in free () from /lib64/libc.so.6
#1 0x00007f5f488cfed2 in g_free (mem=0x5541f689495641d7) at gmem.c:194
#2 0x00007f5f488b47e6 in g_error_free (error=0x55e729f09680 <__libc_csu_init>)
at gerror.c:493
#3 0x000055e729f095f6 in run (command=<optimized out>) at main.c:137
#4 0x000055e729f0940f in main (argc=<optimized out>, argv=<optimized out>)
at main.c:231
So it turns out in my case it's because "Secure" boot breaks hibernation, apparently by design (bug 1518473). This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |