Description of problem: I was doing a search on the commit message and was going forward with Ctrl-G and scrolling around, at some point gitg just crashed. Version-Release number of selected component: gitg-0.2.7-2.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gitg crash_function: gitg_hash_hash_to_sha1 executable: /usr/bin/gitg kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gitg_hash_hash_to_sha1 at gitg-hash.c:82 #1 gitg_revision_get_sha1 at gitg-revision.c:204 #2 make_stats_table at gitg-revision-details-panel.c:344 #3 on_shell_end at gitg-revision-details-panel.c:442 #8 update_details at gitg-revision-details-panel.c:716 #9 reload at gitg-revision-details-panel.c:893 #10 set_revision at gitg-revision-details-panel.c:935 #11 on_selection_changed at gitg-window.c:354 #12 _g_closure_invoke_va at gclosure.c:840 #15 gtk_tree_selection_unselect_all at gtktreeselection.c:1286 Potential duplicate: bug 707096
Created attachment 874134 [details] File: backtrace
Created attachment 874135 [details] File: cgroup
Created attachment 874136 [details] File: core_backtrace
Created attachment 874137 [details] File: dso_list
Created attachment 874138 [details] File: environ
Created attachment 874139 [details] File: exploitable
Created attachment 874140 [details] File: limits
Created attachment 874141 [details] File: maps
Created attachment 874142 [details] File: open_fds
Created attachment 874143 [details] File: proc_pid_status
Created attachment 874144 [details] File: var_log_messages
Another user experienced a similar problem: I started gitg and started to type in the "search" window while the history was still loading. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gitg crash_function: gitg_hash_hash_to_sha1 executable: /usr/bin/gitg kernel: 3.14.8-200.fc20.x86_64 package: gitg-0.2.7-2.fc20 reason: gitg killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I am able to consistently reproduce this by entering a string in the search field, and then backspacing until the search field is empty + 1 more backspace.
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.