Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1045455

Summary: chromium proc name is wrongly named "chromium-browse"
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Pelka <tpelka>
Component: procpsAssignee: Jaromír Cápík <jcapik>
Status: CLOSED NOTABUG QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: albert, ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-08 13:01:43 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 Tomas Pelka 2013-12-20 13:13:55 UTC
Description of problem:
pgrep reports different process names for chromium-browser

$ pgrep -l chromium
21427 chromium-browse
21432 chromium-browse
21434 chromium-browse
21437 chromium-browse
21480 chromium-browse
21497 chromium-browse
21502 chromium-browse
21508 chromium-browse
21513 chromium-browse
21518 chromium-browse
21523 chromium-browse
21794 chromium-browse

$ ps aux | grep chromium
tpelka   21427 65.8  7.6 1247456 456384 ?      SLl  14:07   1:12 /opt/chromium-browser/chromium-browser --enable-plugins --enable-extensions --enable-user-scripts --enable-printing --enable-sync --auto-ssl-client-auth --ppapi-flash-path=/opt/chromium-browser/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.9.900.170
....

$ ps -e | grep chromium
21427 ?        00:01:12 chromium-browse
21432 ?        00:00:00 chromium-browse
21434 ?        00:00:00 chromium-browse
21437 ?        00:00:00 chromium-browse
21480 ?        00:00:00 chromium-browse
21497 ?        00:00:00 chromium-browse
21502 ?        00:00:00 chromium-browse
21508 ?        00:00:00 chromium-browse
21513 ?        00:00:00 chromium-browse
21518 ?        00:00:00 chromium-browse
21523 ?        00:00:00 chromium-browse
21794 ?        00:00:00 chromium-browse

$ cat /proc/21427/status | grep Name
Name:	chromium-browse 

Version-Release number of selected component (if applicable):
procps-3.2.8-25.el6.x86_64
chromium-31.0.1650.63-1.el6_5.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
chromium process is called "chromium-browse"

Expected results:
The name should be "chromium-browser"

Additional info:

Comment 1 Jaromír Cápík 2014-01-08 13:01:43 UTC
As proces names are limited to 15 chars + null terminator, this seems to be correct behaviour. Closing.