Version-Release number of selected component: man-db-2.6.5-5.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mandb -q crash_function: _IO_default_xsputn executable: /usr/bin/mandb kernel: 3.16.6-203.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 _IO_default_xsputn at genops.c:480 #1 _IO_new_file_xsputn at fileops.c:1348 #2 _IO_fwrite at iofwrite.c:43 #3 decompress_zlib at decompress.c:61 #4 pipecmd_exec at pipeline.c:740 #5 pipeline_start at pipeline.c:1515 #6 ult_src at ult_src.c:380 #7 test_manfile at check_mandirs.c:240 #8 add_dir_entries at check_mandirs.c:346 #9 testmandirs at check_mandirs.c:517
Created attachment 956156 [details] File: backtrace
Created attachment 956157 [details] File: cgroup
Created attachment 956158 [details] File: core_backtrace
Created attachment 956159 [details] File: dso_list
Created attachment 956160 [details] File: environ
Created attachment 956161 [details] File: limits
Created attachment 956162 [details] File: maps
Created attachment 956163 [details] File: open_fds
Created attachment 956164 [details] File: proc_pid_status
Created attachment 956165 [details] File: var_log_messages
Created attachment 956166 [details] File: exploitable
Hi Pavel, thank you for reporting the crash. Has this issue occurred more than once? Can you reproduce it? Regards Jan
This crash is with libpipeline 1.2.4. It's hard to say for sure without reproducing under valgrind, but I think this might be the bug I fixed here: http://git.savannah.gnu.org/cgit/libpipeline.git/commit/?id=6ade4a2d378b29332ab51d90d6b3caae08824f31
Thanks Colin. I will add the commit into f20. In any case, this bug can be then reopened if the problem occurs again.
libpipeline-1.2.4-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libpipeline-1.2.4-3.fc20
Jan, Abrt applet reported this crash twice, but I don't know why it crashed. I've just unlocked laptop and saw abrt notification.
Package libpipeline-1.2.4-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libpipeline-1.2.4-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-14861/libpipeline-1.2.4-3.fc20 then log in and leave karma (feedback).
Pavel, if this issue still occurs, don't hesitate to reopen this bug again :). Regards Jan
Thank you!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
libpipeline-1.2.4-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.