Bug 1376205 - Firefox always crashes at startup when using Oxygen-gtk3 theme
Summary: Firefox always crashes at startup when using Oxygen-gtk3 theme
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: oxygen-gtk3
Version: 7.2
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-14 20:58 UTC by Diego
Modified: 2016-11-04 01:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 01:29:26 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 331020 0 None None None 2016-09-14 20:58:55 UTC
Red Hat Product Errata RHBA-2016:2236 0 normal SHIPPED_LIVE kde-workspace bug fix and enhancement update 2016-11-03 13:28:08 UTC

Description Diego 2016-09-14 20:58:56 UTC
Description of problem:
Firefox always crashes at startup when using Oxygen-gtk3 theme (default in KDE).
Using other themes solves the problem

Version-Release number of selected component (if applicable):
# rpm -q oxygen-gtk3 
oxygen-gtk3-1.1.4-3.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. set oxygen-gtk3 theme
2. start firefox

Actual results:
Crash

Expected results:
No crash

Additional info:
Useful links (with patch fixing the problem):
https://bugs.kde.org/show_bug.cgi?id=331020
https://bugzilla.mozilla.org/show_bug.cgi?id=1268185
https://bugzilla.redhat.com/show_bug.cgi?id=1065099

So overall it should be just a matter of applying a patch.

Comment 4 Jan Grulich 2016-09-19 12:22:00 UTC
Fixed in oxygen-gtk3-1.1.4-5.el7.

Comment 9 errata-xmlrpc 2016-11-04 01:29:26 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://rhn.redhat.com/errata/RHBA-2016-2236.html


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