Bug 1035764

Summary:	Crashes with certain Google Drive documents
Product:	[Fedora] Fedora	Reporter:	Debarshi Ray <debarshir>
Component:	webkitgtk3	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	awilliam, fedora, kalevlember, mclasen, tpopela
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	AcceptedFreezeException
Fixed In Version:	webkitgtk3-2.2.2-2.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-04 16:53:45 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:
Bug Depends On:
Bug Blocks:	980657

Description Debarshi Ray 2013-11-28 12:28:25 UTC

Certain Google Drive documents crash with webkitgtk-2.2.x (Fedora 20 / GNOME 3.10), while they did not with webkitgtk-2.0.x (Fedora 19 / GNOME 3.8).

See the GNOME and WebKit bugs for more details on how to reproduce.

I have webkitgtk3-2.2.2-1.fc20

Comment 1 Fedora Update System 2013-11-28 16:01:19 UTC

webkitgtk3-2.2.2-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/webkitgtk3-2.2.2-2.fc20

Comment 2 Adam Williamson 2013-11-28 18:03:07 UTC

Proposing as a freeze exception issue (suggested by rishi): this is a function you might reasonably use on a live image, so it'd be nice to fix it.

Comment 3 Adam Williamson 2013-12-02 19:03:21 UTC

Discussed at 2013-12-02 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-02/f20-blocker-review-%234.2013-12-02-17.02.log.txt . Accepted as a freeze exception issue per justification in description, fix looks to be well tested.

Comment 4 Fedora Update System 2013-12-04 16:53:45 UTC

webkitgtk3-2.2.2-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.