Bug 1109798

Summary: [abrt] gitg: g_settings_set_property(): gitg killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Mikko Tiihonen <mikko.tiihonen>
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: 22CC: icq, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4c0bdaa9488f2c13b7ac53964b0e3b4331f74e5b
Whiteboard: abrt_hash:5b091d36384dcb71853daad9cfe9866b0ef8c407
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:48:10 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mikko Tiihonen 2014-06-16 11:44:57 UTC 
Description of problem:
The program does not even start. It crashes immediately.

Version-Release number of selected component:
gitg-0.3.2-2.fc21

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        gitg
crash_function: g_settings_set_property
executable:     /usr/bin/gitg
kernel:         3.15.0-0.rc8.git4.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_set_property at gsettings.c:481
 #3 object_set_property at gobject.c:1385
 #4 g_object_new_internal at gobject.c:1768
 #5 g_object_new_valist at gobject.c:1991
 #7 g_settings_new at gsettings.c:853
 #8 gitg_application_real_startup at /home/jesse/git/gnome/gitg/gitg/gitg-application.vala:276
 #9 _g_closure_invoke_va at gclosure.c:831
 #12 g_application_register at gapplication.c:1808
 #13 g_application_real_local_command_line at gapplication.c:900
 #14 gitg_application_real_local_command_line at /home/jesse/git/gnome/gitg/gitg/gitg-application.vala:137
Comment 1 Mikko Tiihonen 2014-06-16 11:45:02 UTC 
Created attachment 909085 [details]
File: backtrace
Comment 2 Mikko Tiihonen 2014-06-16 11:45:04 UTC 
Created attachment 909086 [details]
File: cgroup
Comment 3 Mikko Tiihonen 2014-06-16 11:45:06 UTC 
Created attachment 909087 [details]
File: core_backtrace
Comment 4 Mikko Tiihonen 2014-06-16 11:45:09 UTC 
Created attachment 909088 [details]
File: dso_list
Comment 5 Mikko Tiihonen 2014-06-16 11:45:11 UTC 
Created attachment 909089 [details]
File: environ
Comment 6 Mikko Tiihonen 2014-06-16 11:45:13 UTC 
Created attachment 909090 [details]
File: limits
Comment 7 Mikko Tiihonen 2014-06-16 11:45:16 UTC 
Created attachment 909091 [details]
File: maps
Comment 8 Mikko Tiihonen 2014-06-16 11:45:19 UTC 
Created attachment 909092 [details]
File: open_fds
Comment 9 Mikko Tiihonen 2014-06-16 11:45:21 UTC 
Created attachment 909093 [details]
File: proc_pid_status
Comment 10 Mikko Tiihonen 2014-06-16 11:45:23 UTC 
Created attachment 909094 [details]
File: var_log_messages
Comment 11 Jaroslav Reznik 2015-03-03 16:02:02 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 12 Fedora End Of Life 2016-07-19 11:48:10 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.