Version-Release number of selected component: mc-4.8.6-1.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: /usr/bin/mc -P /tmp/mc-pau/mc.pwd.2011 crash_function: g_malloc kernel: 3.5.4-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #2 g_malloc at gmem.c:159 : #3 g_strdup at gstrfuncs.c:356 : #4 g_strdupv at gstrfuncs.c:2431 : #5 g_key_file_init at gkeyfile.c:574 : #6 g_key_file_new at gkeyfile.c:631 : #7 mc_config_init at common.c:115 : #8 dlg_read_history at dialog.c:168 : #9 init_dlg at dialog.c:1228 : #10 do_create_message at wtools.c:130 : #11 fg_message at wtools.c:147
Created attachment 619697 [details] File: core_backtrace
Created attachment 619698 [details] File: environ
Created attachment 619699 [details] File: backtrace
Created attachment 619700 [details] File: limits
Created attachment 619701 [details] File: cgroup
Created attachment 619702 [details] File: maps
Created attachment 619703 [details] File: dso_list
Created attachment 619704 [details] File: var_log_messages
Created attachment 619705 [details] File: open_fds
Hmmm, this one is interesting. MC is likely not the culprit here as it only calls a simple g_key_file_new() initialization function without any arguments. The segfault itself is caused by either glib2 or glibc. Reassigning to glib2 to investigate. Feel free to further reassign to glibc if appropriate. Thanks!
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.