Description of problem: powerline maybe? Version-Release number of selected component: powerline-0.0.1-6.20140226git70a94e.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/python /bin/powerline tmux left crash_function: update_refs executable: /usr/bin/python2.7 kernel: 3.13.6-200.fc20.x86_64 runlevel: N 3 type: CCpp uid: 1000 Truncated backtrace: warning: core file may not match specified executable file. [New LWP 15286] warning: File "/var/cache/abrt-di/usr/lib/debug/usr/lib64/libpython2.7.so.1.0.debug-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py". To enable execution of this file add add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug/usr/lib64/libpython2.7.so.1.0.debug-gdb.py line to your configuration file "/home/john/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/john/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/python /bin/powerline tmux left'. Program terminated with signal SIGSEGV, Segmentation fault. #0 update_refs (containers=<optimized out>) at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:400 400 /usr/src/debug/Python-2.7.5/Modules/gcmodule.c: No such file or directory. Thread 1 (Thread 0x7f147fca8740 (LWP 15286)): #0 update_refs (containers=<optimized out>) at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:400 gc = 0xd007f147fb2a5d0 #1 collect (generation=0) at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:998 i = <optimized out> m = 0 n = 0 young = <optimized out> old = 0x7f147fa9f290 <generations+48> unreachable = {gc = {gc_next = 0xd0, gc_prev = 0x16c, gc_refs = 115}, dummy = <invalid float value>} finalizers = {gc = {gc_next = 0xf84530, gc_prev = 0x7f147f7850ca <_PyString_Eq+42>, gc_refs = 140737463596448}, dummy = <invalid float value>}
Created attachment 874948 [details] File: backtrace
Created attachment 874949 [details] File: cgroup
Created attachment 874950 [details] File: core_backtrace
Created attachment 874951 [details] File: dso_list
Created attachment 874952 [details] File: environ
Created attachment 874953 [details] File: exploitable
Created attachment 874954 [details] File: limits
Created attachment 874955 [details] File: maps
Created attachment 874956 [details] File: open_fds
Created attachment 874957 [details] File: proc_pid_status
Created attachment 874958 [details] File: var_log_messages
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.