Description of problem: Opened gitg and started to search commit, typing the word 'negative', letter by letter. Reproducible: sometimes. I tried to repeat it twice, and one of two times it segfaulted again. Version-Release number of selected component: gitg-0.2.7-1.fc19 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gitg crash_function: gitg_hash_hash_to_sha1 executable: /usr/bin/gitg kernel: 3.14.4-100.fc19.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:1294 Potential duplicate: bug 707096
Created attachment 909535 [details] File: backtrace
Created attachment 909536 [details] File: cgroup
Created attachment 909537 [details] File: core_backtrace
Created attachment 909538 [details] File: dso_list
Created attachment 909539 [details] File: environ
Created attachment 909540 [details] File: exploitable
Created attachment 909541 [details] File: limits
Created attachment 909542 [details] File: maps
Created attachment 909543 [details] File: open_fds
Created attachment 909544 [details] File: proc_pid_status
Created attachment 909545 [details] File: var_log_messages
I think .git/config file contents can help debugging, this occured on viewing ReviewBoard git repo. Here it is: [core] >---repositoryformatversion = 0 >---filemode = true >---bare = false >---logallrefupdates = true [remote "origin"] >---url = https://github.com/reviewboard/reviewboard.git >---fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] >---remote = origin >---merge = refs/heads/master [branch "release-1.7.x"] >---remote = origin >---merge = refs/heads/release-1.7.x
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.