Version-Release number of selected component: fish-2.1.0-11.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/fish crash_function: fresetlockfiles executable: /usr/bin/fish kernel: 3.15.10-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 fresetlockfiles at ../nptl/sysdeps/unix/sysv/linux/fork.c:48 #1 __libc_fork at ../nptl/sysdeps/unix/sysv/linux/fork.c:176 #2 __spawni at ../sysdeps/posix/spawni.c:108 #3 __posix_spawn at spawn.c:30 #4 exec_job at exec.cpp:1407 #5 parser_t::eval_job at parser.cpp:2444 #6 parser_t::eval at parser.cpp:2636 #7 exec_subshell_internal at exec.cpp:1560 #8 exec_subshell at exec.cpp:1605 #9 expand_cmdsubst at expand.cpp:1379
Created attachment 934950 [details] File: backtrace
Created attachment 934951 [details] File: cgroup
Created attachment 934952 [details] File: core_backtrace
Created attachment 934953 [details] File: dso_list
Created attachment 934954 [details] File: environ
Created attachment 934955 [details] File: exploitable
Created attachment 934956 [details] File: limits
Created attachment 934957 [details] File: maps
Created attachment 934958 [details] File: open_fds
Created attachment 934959 [details] File: proc_pid_status
Created attachment 934960 [details] File: var_log_messages
This smells like a glibc bug. Were you doing anything unusual at the time?
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.
This is still happening. See: https://retrace.fedoraproject.org/faf/reports/601241/ This really smells like a glibc bug to me. I'm assigning to glibc. Glibc people, if you don't think this is a glibc bug, please reassign it back to me.
I'm closing this. I haven't gotten any reports about it on newer fish/glibc combinations. I'll file a new bug if I see it again.