Bug 1222651

Summary: [abrt] gnome-contacts: _g_log_abort(): gnome-contacts killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Peter <peter>
Component: gnome-contactsAssignee: Elad Alfassa <elad>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: alexl, elad, fedora, fedoraparked
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7d816c660a7a767abc5e9ae19aa507ffde87b101
Whiteboard: abrt_hash:4cd14979e77f9d20033d1516570b0ce2180bc123
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:09:13 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Peter 2015-05-18 18:17:21 UTC 
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
Comment 1 Peter 2015-05-18 18:17:25 UTC 
Created attachment 1026799 [details]
File: backtrace
Comment 2 Peter 2015-05-18 18:17:26 UTC 
Created attachment 1026800 [details]
File: cgroup
Comment 3 Peter 2015-05-18 18:17:28 UTC 
Created attachment 1026802 [details]
File: core_backtrace
Comment 4 Peter 2015-05-18 18:17:30 UTC 
Created attachment 1026803 [details]
File: dso_list
Comment 5 Peter 2015-05-18 18:17:31 UTC 
Created attachment 1026804 [details]
File: environ
Comment 6 Peter 2015-05-18 18:17:33 UTC 
Created attachment 1026805 [details]
File: limits
Comment 7 Peter 2015-05-18 18:17:36 UTC 
Created attachment 1026806 [details]
File: maps
Comment 8 Peter 2015-05-18 18:17:38 UTC 
Created attachment 1026807 [details]
File: mountinfo
Comment 9 Peter 2015-05-18 18:17:39 UTC 
Created attachment 1026808 [details]
File: namespaces
Comment 10 Peter 2015-05-18 18:17:40 UTC 
Created attachment 1026809 [details]
File: open_fds
Comment 11 Peter 2015-05-18 18:17:42 UTC 
Created attachment 1026810 [details]
File: proc_pid_status
Comment 12 Peter 2015-05-18 18:17:43 UTC 
Created attachment 1026811 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 14:09:13 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.