Bug 1310254 - chromium-browser.sh has verbose flag on - fills up .xsession-errors file and user quota
chromium-browser.sh has verbose flag on - fills up .xsession-errors file and ...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: chromium-browser (Show other bugs)
All Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Tomas Popela
Tomas Pelka
Depends On:
  Show dependency treegraph
Reported: 2016-02-19 16:35 EST by Peter Lannigan
Modified: 2017-12-06 05:53 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-06 05:53:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Lannigan 2016-02-19 16:35:09 EST
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):

How reproducible:

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

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 02:20:36 EST
Yes, there is a mistake in the SPEC file. It will be fixed with the next release.
Comment 3 Jan Kurik 2017-12-06 05:53:52 EST
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:


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:


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