Bug 1310254

Summary: chromium-browser.sh has verbose flag on - fills up .xsession-errors file and user quota
Product: Red Hat Enterprise Linux 6 Reporter: Peter Lannigan <peter.lannigan>
Component: chromium-browserAssignee: Tomas Popela <tpopela>
Status: CLOSED WONTFIX QA Contact: Tomas Pelka <tpelka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 10:53:52 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 Peter Lannigan 2016-02-19 21:35:09 UTC 
Description of problem:
Line 47 of /opt/chromium-browser/chromium-browswer.sh specifies the --v=2 flag which apparently is verbose logging (undocumented feature?).  The verbose logging goes to ~/.xsession-errors and files up the user's quota.

Version-Release number of selected component (if applicable):
chromium-browser-48.0.2564.109-1.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start chromium-browser in Gnome
2. watch ~/.xession-errors
3.

Actual results:
Very large ~/.xsession-errors file

Expected results:
Only a few lines in ~/.xsession-errors relating to chromium-browser running.

Additional info:
Comment 2 Tomas Popela 2016-02-22 07:20:36 UTC 
Yes, there is a mistake in the SPEC file. It will be fixed with the next release.
Comment 3 Jan Kurik 2017-12-06 10:53:52 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/