Bug 1084475

Summary: [abrt] gnome-contacts: g_variant_n_children(): gnome-contacts-search-provider killed by SIGSEGV
Product: [Fedora] Fedora Reporter: miguel rodriguez <bokerones.fritos>
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, fedoraparked
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7f1d986befb7d211c0450b56f51122f359dcad33
Whiteboard: abrt_hash:be1d05463b5328050e73e8f63baa52c6c039ff62
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:17:57 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description miguel rodriguez 2014-04-04 12:43:35 UTC
Description of problem:
I started gnome-contacts in tty and clic on icon "contacts" blue book, but crashes...

Version-Release number of selected component:
gnome-contacts-3.12.0-1.fc21

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-contacts-search-provider
crash_function: g_variant_n_children
executable:     /usr/libexec/gnome-contacts-search-provider
kernel:         3.14.0-1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 g_variant_n_children at /lib64/libglib-2.0.so.0
 #1 g_variant_get_child_value at /lib64/libglib-2.0.so.0
 #2 append_value_to_blob at /lib64/libgio-2.0.so.0

Comment 1 miguel rodriguez 2014-04-04 12:43:40 UTC
Created attachment 882672 [details]
File: backtrace

Comment 2 miguel rodriguez 2014-04-04 12:43:42 UTC
Created attachment 882673 [details]
File: cgroup

Comment 3 miguel rodriguez 2014-04-04 12:43:48 UTC
Created attachment 882674 [details]
File: core_backtrace

Comment 4 miguel rodriguez 2014-04-04 12:43:50 UTC
Created attachment 882675 [details]
File: dso_list

Comment 5 miguel rodriguez 2014-04-04 12:43:53 UTC
Created attachment 882676 [details]
File: environ

Comment 6 miguel rodriguez 2014-04-04 12:43:55 UTC
Created attachment 882677 [details]
File: exploitable

Comment 7 miguel rodriguez 2014-04-04 12:43:57 UTC
Created attachment 882678 [details]
File: limits

Comment 8 miguel rodriguez 2014-04-04 12:43:59 UTC
Created attachment 882679 [details]
File: maps

Comment 9 miguel rodriguez 2014-04-04 12:44:03 UTC
Created attachment 882680 [details]
File: open_fds

Comment 10 miguel rodriguez 2014-04-04 12:44:05 UTC
Created attachment 882681 [details]
File: proc_pid_status

Comment 11 miguel rodriguez 2014-04-04 12:44:07 UTC
Created attachment 882682 [details]
File: var_log_messages

Comment 12 Jaroslav Reznik 2015-03-03 15:39:55 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 13 Fedora End Of Life 2016-07-19 11:17:57 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.