Hide Forgot
Description of problem: I think this happened during a drag and drop operation. (By the way, it took about half an hour to download and install the relevant debuginfo packages to get a backtrace... maybe the ABRT 'what did you just do' screen should be done as soon as possible, rather than after all that?) Version-Release number of selected component: gthumb-3.2.4-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gthumb crash_function: strncmp executable: /usr/bin/gthumb kernel: 3.15.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (7 frames) #0 strncmp at ../sysdeps/x86_64/strcmp.S:209 #1 gth_file_source_supports_scheme at gth-file-source.c:921 #2 get_monitor_file_source_for_file at gth-folder-tree.c:416 #3 _gth_folder_tree_remove_from_monitor at gth-folder-tree.c:434 #4 update_monitored_locations at gth-folder-tree.c:534 #9 g_main_context_iteration at gmain.c:3774 #10 g_application_run at gapplication.c:1635
Created attachment 920687 [details] File: backtrace
Created attachment 920688 [details] File: cgroup
Created attachment 920689 [details] File: core_backtrace
Created attachment 920690 [details] File: dso_list
Created attachment 920691 [details] File: environ
Created attachment 920692 [details] File: exploitable
Created attachment 920693 [details] File: limits
Created attachment 920694 [details] File: maps
Created attachment 920695 [details] File: open_fds
Created attachment 920696 [details] File: proc_pid_status
Created attachment 920697 [details] File: var_log_messages
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.