Description of problem: Version-Release number of selected component: xfe-2.1.1-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: xfi killed by SIGABRT journald_cursor: s=571c785a527648c08fa6a1bc82c5e937;i=2d8c0bb;b=e6d15c87827d4894b10c6fd3639635cb;m=43003e5de9;t=646b6f15d58ac;x=e3941d2b52d3a369 executable: /usr/libexec/xfe/xfi cmdline: xfi /home/mrmeval/Pictures/pretty/new_AI/download $'(1).jpeg' cgroup: 0::/user.slice/user-1000.slice/user/app.slice/thunar.service rootdir: / uid: 1000 kernel: 6.17.12-200.fc42.x86_64 package: xfe-2.1.1-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: FX::fxerror comment: Truncated backtrace: Thread no. 1 (6 frames) #4 FX::fxerror at /usr/src/debug/fox-1.6.59-1.fc42.x86_64/src/fxutils.cpp:220 #5 FX::FXDCWindow::drawImage at /usr/src/debug/fox-1.6.59-1.fc42.x86_64/src/FXDCWindow.cpp:731 #6 FX::FXImageView::onPaint at /usr/src/debug/fox-1.6.59-1.fc42.x86_64/src/FXImageView.cpp:157 #7 FX::FXApp::dispatchEvent at /usr/src/debug/xfe-2.1.1-1.fc42.x86_64/src/foxhacks.cpp:1898 #8 FX::FXApp::runOneEvent at /usr/src/debug/fox-1.6.59-1.fc42.x86_64/src/FXApp.cpp:3135 #9 FX::FXApp::run at /usr/src/debug/fox-1.6.59-1.fc42.x86_64/src/FXApp.cpp:3092
Created attachment 2120285 [details] File: proc_pid_status
Created attachment 2120286 [details] File: maps
Created attachment 2120287 [details] File: limits
Created attachment 2120288 [details] File: environ
Created attachment 2120289 [details] File: open_fds
Created attachment 2120290 [details] File: mountinfo
Created attachment 2120291 [details] File: os_info
Created attachment 2120292 [details] File: cpuinfo
Created attachment 2120293 [details] File: core_backtrace
Created attachment 2120294 [details] File: dso_list
Created attachment 2120295 [details] File: var_log_messages
Created attachment 2120296 [details] File: backtrace
XFE-XFE a file manager will call XFE-XFI an image viewer when a picture is clicked on. When I use the arrow keys to view more pictures and arrow to a text file XFE-XFI will give an error and exit and XFE-XFE crashes. I only get an error when XFE-XFI is called and stumbles over a text file or I try to use file->open to open a text file. I am not sure these are actively maintained yet.
I don't see xfi abort()ing when clicking arrow keys to move chosen file moved into text file. I guess xfi was trying to open really invalid image file. * Can you guess what file xfi was actually trying to open when this crash happened? And can you upload the file somewhere?
(In reply to Mamoru TASAKA from comment #14) > I don't see xfi abort()ing when clicking arrow keys to move chosen file > moved into text file. > I guess xfi was trying to open really invalid image file. > > * Can you guess what file xfi was actually trying to open when this crash > happened? And can you upload the file somewhere Once I start XFE-XFE and then try go to a picture folder. I right click on a picture to view it. This calls XFE-XFI. When using XFE-XFI and arrow key to view image files and it tries to access a text file I get an error from XFE-XFI. XFE-XFE may crash. It does not matter what is in the file that I can tell. XFE-XFE may not issue a crash at first but it will eventually. On the a.txt file created below I got it to crash consistently. To create the file just echo hi > a.txt I am not sure what is causing this as XFE-XFE file manager calls XFE-XFI image viewer. THe image viewer will close when I close on an unsupported type:txt modal window and I get a crash notice for XFE-XFI but abrt has what is recorded here. Abrt won't have the error until XFE-XFE is closed. It also fails to list the last file viewed.
A work around 1)Set another image viewer that does not stumble over other file types in XFE in Edit->Preferences-Filetypes. 2)Check the box in XFI under Preferences to 'Filter Images' this will no longer attempt to open all unknown to XFI file types and remove them from XFI's file list if that file list is active. Thanks for your help. I'm not sure it's easy to find.
I am going to add some workaround for xfi for now (but it is different from what you said).
FEDORA-2026-d9d0580121 (xfe-2.1.2-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-d9d0580121
FEDORA-2026-e2e7008733 (xfe-2.1.2-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-e2e7008733
FEDORA-2026-e2e7008733 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-e2e7008733` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e2e7008733 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-d9d0580121 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-d9d0580121` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d9d0580121 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-d9d0580121 (xfe-2.1.2-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-e2e7008733 (xfe-2.1.2-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.