Description of problem: Crash after a selecting a certain contact. Which exists in two different address books (but I'm not sure if that was the reason). Version-Release number of selected component: gnome-contacts-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-contacts --gapplication-service crash_function: _g_log_abort executable: /usr/bin/gnome-contacts global_pid: 16051 kernel: 4.0.3-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:315 #6 __glXSendError at glx_error.c:64 #7 GetDrawableAttribute at glx_pbuffer.c:334 #8 _cogl_winsys_onscreen_get_buffer_age at winsys/cogl-winsys-glx.c:1685 #9 clutter_stage_cogl_redraw at cogl/clutter-stage-cogl.c:477 #10 clutter_stage_gdk_redraw at gdk/clutter-stage-gdk.c:468 #11 clutter_stage_do_redraw at clutter-stage.c:1130 #12 _clutter_stage_do_update at clutter-stage.c:1186 #13 master_clock_update_stage at gdk/clutter-master-clock-gdk.c:223 #14 clutter_master_clock_gdk_update at gdk/clutter-master-clock-gdk.c:280
Created attachment 1026799 [details] File: backtrace
Created attachment 1026800 [details] File: cgroup
Created attachment 1026802 [details] File: core_backtrace
Created attachment 1026803 [details] File: dso_list
Created attachment 1026804 [details] File: environ
Created attachment 1026805 [details] File: limits
Created attachment 1026806 [details] File: maps
Created attachment 1026807 [details] File: mountinfo
Created attachment 1026808 [details] File: namespaces
Created attachment 1026809 [details] File: open_fds
Created attachment 1026810 [details] File: proc_pid_status
Created attachment 1026811 [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.