Bug 1503624

Summary: webkitgtk4: Crash on Google login page when a11y is active
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: webkitgtk4Assignee: Tomas Popela <tpopela>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/9f4f4f3bdbb0931576bc0821723ef665177745d5/
Whiteboard:
Fixed In Version: webkitgtk4-2.20.4-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:19:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vladimir Benes 2017-10-18 13:40:00 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/9f4f4f3bdbb0931576bc0821723ef665177745d5/

Comment 1 Vladimir Benes 2017-10-18 13:40:46 UTC
we don't have anything more than backtrace, if you need anything more I will attach whole sosreport

Comment 3 Vladimir Benes 2017-10-18 13:42:43 UTC
it's crashing again when you press NEXT after entering credentials in g-o-a for google account, it may as well crash after password is entered and we are waiting for ALLOW

Comment 4 Vladimir Benes 2017-10-18 17:04:22 UTC
ok, so this should be bt captured just after first error in terminal with G_DEBUG=fatal-warnings:
https://paste.fedoraproject.org/paste/TLYHQhLyuSQhT6iv7UZ6XQ

Comment 7 Vladimir Benes 2018-08-31 12:21:10 UTC
This looks good now. One minor bug where we need to refocus to refresh a11y structure is still there but the crash is definitely gone.

Comment 9 errata-xmlrpc 2018-10-30 10:19:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3140