Description of problem: Do not know. I was away from the machine at the time. It had tmux running in the forground. Version-Release number of selected component: bash-4.2.45-4.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: sh -c 'eval $POWERLINE_COMMAND tmux left' crash_function: read_alias_file executable: /usr/bin/bash kernel: 3.13.5-200.fc20.x86_64 runlevel: N 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 read_alias_file at localealias.c:258 #1 _nl_expand_alias at localealias.c:188 #2 _nl_find_domain at finddomain.c:118 #3 __dcigettext at dcigettext.c:626 #4 __dcgettext at dcgettext.c:52 #5 notify_of_job_status at jobs.c:3549 #6 notify_and_cleanup at jobs.c:2664 #7 wait_for at jobs.c:2611 #8 execute_command_internal at execute_cmd.c:787 #9 parse_and_execute at evalstring.c:319
Created attachment 872288 [details] File: backtrace
Created attachment 872289 [details] File: cgroup
Created attachment 872290 [details] File: core_backtrace
Created attachment 872291 [details] File: dso_list
Created attachment 872292 [details] File: environ
Created attachment 872293 [details] File: exploitable
Created attachment 872294 [details] File: limits
Created attachment 872295 [details] File: maps
Created attachment 872296 [details] File: open_fds
Created attachment 872297 [details] File: proc_pid_status
Created attachment 872298 [details] File: var_log_messages
Thanks for the report. Looking at ABRT-generated files, bash actually crashed in one of the functions in the gettext library bash uses. Moving to gettext. Hopefully its maintainer will be able to bring some insight into this.
What info is needed? I have not been able to reproduce this recently...
Sorry, my bad, meant to set needinfo to Daiki.
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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
I am afraid I cannot say anything from the provided backtrace. Perhaps you might want to talk to glibc people if the problem still persists.
John, or anybody, feel free to reopen if this happens again.