Hide Forgot
Description of problem: I was just moving files around. It's the second (or third) time I see this. Version-Release number of selected component: mc-4.8.10-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/mc -P /tmp/mc-dgunchev/mc.pwd.5927 crash_function: gauge_show executable: /usr/bin/mc kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gauge_show at gauge.c:175 #1 file_progress_show at filegui.c:892 #2 panel_operate at file.c:3042 #3 rename_cmd at cmd.c:900 #4 midnight_execute_cmd at midnight.c:1306 #5 buttonbar_callback at buttonbar.c:174 #6 send_message at ../../lib/widget/widget-common.h:162 #7 dlg_try_hotkey at dialog.c:463 #8 dlg_key_event at dialog.c:508 #9 dlg_process_event at dialog.c:1221
Created attachment 836197 [details] File: backtrace
Created attachment 836198 [details] File: cgroup
Created attachment 836199 [details] File: core_backtrace
Created attachment 836200 [details] File: dso_list
Created attachment 836201 [details] File: environ
Created attachment 836202 [details] File: exploitable
Created attachment 836203 [details] File: limits
Created attachment 836204 [details] File: maps
Created attachment 836205 [details] File: open_fds
Created attachment 836206 [details] File: proc_pid_status
Created attachment 836207 [details] File: var_log_messages
Another user experienced a similar problem: I am try to move a directory. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/mc -P /tmp/mc-root/mc.pwd.5690 crash_function: gauge_show executable: /usr/bin/mc kernel: 3.11.10-301.fc20.x86_64 package: mc-4.8.10-2.fc20 reason: mc killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Same here. It happens when I move more or larger files.
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.