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
Created attachment 909085 [details] File: backtrace
Created attachment 909086 [details] File: cgroup
Created attachment 909087 [details] File: core_backtrace
Created attachment 909088 [details] File: dso_list
Created attachment 909089 [details] File: environ
Created attachment 909090 [details] File: limits
Created attachment 909091 [details] File: maps
Created attachment 909092 [details] File: open_fds
Created attachment 909093 [details] File: proc_pid_status
Created attachment 909094 [details] File: var_log_messages
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
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.