Bug 1110294

Summary: [abrt] gitg: gitg_hash_hash_to_sha1(): gitg killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mikhail Veltishchev <dichlofos-mv>
Component: gitgAssignee: Ignacio Casal Quinteiro (nacho) <icq>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: icq, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/24b7889db5c3f056a5d1dbf63deb4639075267fb
Whiteboard: abrt_hash:878ae3cf476fcdbe50cf82f74ea6cb4ce7439489
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-18 11:44:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mikhail Veltishchev 2014-06-17 11:41:46 UTC 
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
Comment 1 Mikhail Veltishchev 2014-06-17 11:41:50 UTC 
Created attachment 909535 [details]
File: backtrace
Comment 2 Mikhail Veltishchev 2014-06-17 11:41:52 UTC 
Created attachment 909536 [details]
File: cgroup
Comment 3 Mikhail Veltishchev 2014-06-17 11:41:55 UTC 
Created attachment 909537 [details]
File: core_backtrace
Comment 4 Mikhail Veltishchev 2014-06-17 11:41:57 UTC 
Created attachment 909538 [details]
File: dso_list
Comment 5 Mikhail Veltishchev 2014-06-17 11:41:59 UTC 
Created attachment 909539 [details]
File: environ
Comment 6 Mikhail Veltishchev 2014-06-17 11:42:01 UTC 
Created attachment 909540 [details]
File: exploitable
Comment 7 Mikhail Veltishchev 2014-06-17 11:42:03 UTC 
Created attachment 909541 [details]
File: limits
Comment 8 Mikhail Veltishchev 2014-06-17 11:42:06 UTC 
Created attachment 909542 [details]
File: maps
Comment 9 Mikhail Veltishchev 2014-06-17 11:42:08 UTC 
Created attachment 909543 [details]
File: open_fds
Comment 10 Mikhail Veltishchev 2014-06-17 11:42:10 UTC 
Created attachment 909544 [details]
File: proc_pid_status
Comment 11 Mikhail Veltishchev 2014-06-17 11:42:12 UTC 
Created attachment 909545 [details]
File: var_log_messages
Comment 12 Mikhail Veltishchev 2014-06-17 11:44:57 UTC 
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
Comment 13 Fedora End Of Life 2015-01-09 21:25:10 UTC 
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.
Comment 14 Fedora End Of Life 2015-02-18 11:44:44 UTC 
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.