Version-Release number of selected component: gitg-3.16.0-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: gitg --no-wd crash_function: g_path_is_absolute executable: /usr/bin/gitg global_pid: 6934 kernel: 4.0.0-1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_path_is_absolute at gfileutils.c:2100 #1 canonicalize_filename at glocalfile.c:205 #2 _g_local_file_new at glocalfile.c:303 #3 g_daemon_vfs_get_file_for_path at gdaemonvfs.c:385 #4 _ggit_repository_wrap at ggit-repository.c:490 #5 ggit_object_get_owner at ggit-object.c:76 #6 gitg_commit_get_diff at /home/garrett/hacking/gnome/gitg/libgitg/gitg-commit.vala:118 #7 gitg_diff_view_update at /home/garrett/hacking/gnome/gitg/libgitg/gitg-diff-view.vala:547 #8 gitg_diff_view_set_commit at /home/garrett/hacking/gnome/gitg/libgitg/gitg-diff-view.vala:131 #13 gtk_widget_map at gtkwidget.c:5054
Created attachment 1019598 [details] File: backtrace
Created attachment 1019599 [details] File: cgroup
Created attachment 1019600 [details] File: core_backtrace
Created attachment 1019601 [details] File: dso_list
Created attachment 1019602 [details] File: environ
Created attachment 1019604 [details] File: limits
Created attachment 1019605 [details] File: maps
Created attachment 1019606 [details] File: mountinfo
Created attachment 1019607 [details] File: namespaces
Created attachment 1019608 [details] File: open_fds
Created attachment 1019609 [details] File: proc_pid_status
Created attachment 1019610 [details] File: var_log_messages
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.