Version-Release number of selected component: gthumb-3.4.1-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: gthumb crash_function: gth_browser_exec_task executable: /usr/bin/gthumb global_pid: 14235 kernel: 4.2.7-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gth_browser_exec_task at gth-browser.c:5519 #1 delete_file_permanently at gth-file-source-vfs.c:664 #2 delete_permanently_response_cb at gth-file-source-vfs.c:679 #7 _g_closure_invoke_va at gclosure.c:864 #10 gtk_button_do_release at gtkbutton.c:1899 #11 gtk_real_button_released at gtkbutton.c:2017 #16 multipress_released_cb at gtkbutton.c:613 #17 ffi_call_unix64 at ../src/x86/unix64.S:76 #18 ffi_call at ../src/x86/ffi64.c:525 #19 g_cclosure_marshal_generic_va at gclosure.c:1600 Potential duplicate: bug 1269016
Created attachment 1112090 [details] File: backtrace
Created attachment 1112091 [details] File: cgroup
Created attachment 1112092 [details] File: core_backtrace
Created attachment 1112094 [details] File: dso_list
Created attachment 1112095 [details] File: environ
Created attachment 1112096 [details] File: exploitable
Created attachment 1112097 [details] File: limits
Created attachment 1112098 [details] File: maps
Created attachment 1112099 [details] File: mountinfo
Created attachment 1112100 [details] File: namespaces
Created attachment 1112101 [details] File: open_fds
Created attachment 1112102 [details] File: proc_pid_status
Created attachment 1112103 [details] File: var_log_messages
Similar problem has been detected: When I open gthumb . Then when I find Duplicates files then when I click the Duplicate file the try to del one of the file it closes and gives this error reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: gthumb crash_function: gth_browser_exec_task executable: /usr/bin/gthumb global_pid: 9637 kernel: 4.3.5-300.fc23.x86_64 package: gthumb-3.4.1-1.fc23 reason: gthumb killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.