Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Local fs on both sides, both folders accessible, current file on original panel (right in this case) was removed. I pressed tab twice, the cursor (bar) did not appear on the right panel, only header/path hilights; Then I pressed up/down arrows and here we are. Version-Release number of selected component: mc-1:4.8.33-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: mc killed by SIGSEGV journald_cursor: s=c3c42670eefd4397b9d2fb1efce7453a;i=22351f;b=c2b3d7aecbf54a94b36cc74db68362fd;m=d2ac1494;t=63d6a5b318cef;x=ceaef2f9fdb3a7d6 executable: /usr/bin/mc cmdline: /usr/bin/mc -P /tmp/mc.pwd.Ocwty7 cgroup: 0::/user.slice/user-1001.slice/user/app.slice/ptyxis-spawn-508d2412-8eb7-4ae3-ae5f-c3686d6e240c.scope rootdir: / uid: 1001 kernel: 6.15.10-200.fc42.x86_64 package: mc-1:4.8.33-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: string_file_size Truncated backtrace: Thread no. 1 (15 frames) #0 string_file_size at filemanager/panel.c:550 #1 format_file at filemanager/panel.c:860 #2 repaint_file at filemanager/panel.c:980 #3 paint_dir at filemanager/panel.c:1124 #4 move_down at filemanager/panel.c:2212 #6 chdir_other_panel at filemanager/panel.c:3106 #7 panel_execute_cmd at filemanager/panel.c:3643 #8 send_message at ../lib/widget/../../lib/widget/widget-common.h:255 #9 group_handle_key at ../lib/widget/group.c:507 #10 group_default_callback at ../lib/widget/group.c:637 #11 dlg_key_event at ../lib/widget/dialog.c:252 #12 dlg_process_event at ../lib/widget/dialog.c:539 #13 frontend_dlg_run at ../lib/widget/dialog.c:321 #14 dlg_run at ../lib/widget/dialog.c:573 #15 do_nc at filemanager/filemanager.c:1826
Created attachment 2105151 [details] File: proc_pid_status
Created attachment 2105152 [details] File: maps
Created attachment 2105153 [details] File: limits
Created attachment 2105154 [details] File: environ
Created attachment 2105155 [details] File: open_fds
Created attachment 2105156 [details] File: mountinfo
Created attachment 2105157 [details] File: os_info
Created attachment 2105158 [details] File: cpuinfo
Created attachment 2105159 [details] File: core_backtrace
Created attachment 2105160 [details] File: exploitable
Created attachment 2105161 [details] File: dso_list
Created attachment 2105162 [details] File: backtrace
I think this might have the same nature as #2425785 and possibly fixed here: https://github.com/MidnightCommander/mc/issues/4761 See discussion here: https://github.com/MidnightCommander/mc/discussions/5088 Probably will be resolved in the next release.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. 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 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.