Hide Forgot
Description of problem: coredumps do not work. worked in F23. kernel: mate-panel[8499]: segfault at 4 ip 00007efcdc7e9c10 sp 00007ffcf5a4b948 error 4 in libgtk-3.so.0.2200.2[7efcdc5e3000+6f0000] systemd[1]: Started Process Core Dump (PID 9469/UID 0). audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@22-9469-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' systemd-coredump[9470]: Failed to generate stack trace: invalid `Elf' handle systemd-coredump[9470]: Process 8499 (mate-panel) of user 500 dumped core. Version-Release number of selected component (if applicable): 229-16.fc24 How reproducible: 100% Steps to Reproduce: 1. cause a crash in a program, for example 2. 3. Actual results: 0-byte file generated at /var/lib/systemd/coredump and no core dump to be found. Expected results: core! Additional info: # cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e 143 GiB free at /var/lib/systemd/coredump coredump.conf [Coredump] Storage=external Compress=no $ ulimit -c unlimited
Yeah, Compress=no is screwed up. It's fixed upstream, but the patches haven't been backported yet. As a work-around, if you enable compression, this should work. I'll mark this as POST (fixed upstream), but it might take a while until the bug is closed.
systemd-coredump: Failed to compress /var/lib/systemd/coredump/.#core.cat.500.b9ea96294d0846f8b78d7487b4f32039.421.1478067386000000000000.lz49efe236051ce0b1c: Invalid argument systemd-coredump: Failed to generate stack trace: invalid `Elf' handle systemd-coredump: Process 421 (cat) of user 500 dumped core. 0-byte file left.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > Yeah, Compress=no is screwed up. It's fixed upstream, but the patches > haven't been backported yet. As a work-around, if you enable compression, > this should work. > > I'll mark this as POST (fixed upstream), but it might take a while until the > bug is closed. Any chance we can get the upstream fix backported to Fedora 24? Thanks.
It seems that setting “Compress=yes” (or leaving it at the default) does not fix this issue. This is with systemd-229-16.fc24.x86_64.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.