Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1513436 - [abrt] [faf] Crash under client_wait_for_connected_thread()
Summary: [abrt] [faf] Crash under client_wait_for_connected_thread()
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-data-server
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL: http://faf.lab.eng.brq.redhat.com/faf...
Whiteboard:
: 1687288 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-15 12:07 UTC by Vladimir Benes
Modified: 2019-03-11 12:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Vladimir Benes 2017-11-15 12:07:48 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/cd5df593e1638b0509a0a6dfc1cffcdb5a2ecf30/

I see this in beaker, not sure if it's related:
[ 6598.183912] pool[31897]: segfault at 1 ip 00007fb85c13d2c7 sp 00007fb82f593840 error 4 in libglib-2.0.so.0.5400.2[7fb85c0d6000+111000]

Comment 1 Milan Crha 2017-11-15 14:40:57 UTC
Backtrace from the FAF:

   g_slice_alloc
   parse
   parse
   g_variant_parse
   book_client_process_properties
   book_client_retrieve_properties_sync
   client_wait_for_connected_thread
   g_task_thread_pool_thread
   g_thread_pool_thread_proxy
   g_thread_proxy
   start_thread
   __clone

Comment 6 Milan Crha 2019-02-11 13:10:56 UTC
I tried to find a reproducer for this, with a little test application, but no luck so far.

Comment 7 Milan Crha 2019-03-11 12:23:48 UTC
*** Bug 1687288 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.