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 2026892

Summary: bashrc: Don't set up VTE-specific PROMPT_COMMAND
Product: Red Hat Enterprise Linux 9 Reporter: Debarshi Ray <debarshir>
Component: setupAssignee: Martin Osvald 🛹 <mosvald>
Status: CLOSED ERRATA QA Contact: Petr Dancak <pdancak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: pdancak
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: setup-2.13.7-7.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 11:22:32 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 Debarshi Ray 2021-11-26 11:23:23 UTC
First of all, VTE ships its own Bash configuration snippet in /etc/profile. /vte.sh that already does this and provides the definition of the __vte_prompt_command function. So it's better to let VTE own its own configuration.

Secondly, this creates problems in interactive Bash instances running inside a container that doesn't have VTE installed but has the VTE_VERSION environment variable set, because PROMPT_COMMAND tries to access a missing __vte_prompt_command function. This is observed in Toolbox containers created from the Red Hat Universal Base Image. Toolbox containers inherit environment variables like TERM and VTE_VERSION from the host so that interactive shells inside the container are configured like the ones on the host. However, UBI doesn't have /etc/profile.d/vte.sh. Hence, instead of silently ignoring the VTE specific configuration bits, PROMPT_COMMAND ends up trying to access a missing __vte_prompt_command function.

[ This is important because we are going to ship Toolbox in RHEL 9.0. ]

Comment 1 Debarshi Ray 2021-11-26 11:28:32 UTC
For what it's worth, we are now shipping this in Fedora >= 35.

Comment 2 Debarshi Ray 2022-01-07 18:25:57 UTC
Ping.

Comment 3 Debarshi Ray 2022-02-03 19:56:52 UTC
Ping.

Comment 4 Debarshi Ray 2022-03-19 11:31:25 UTC
Ping

Comment 5 Martin Osvald 🛹 2022-03-22 13:50:34 UTC
(In reply to Debarshi Ray from comment #4)
> Ping

This is planned to get fixed in RHEL9.1

Comment 8 Debarshi Ray 2022-05-12 15:43:05 UTC
Thanks for getting this done, Martin!  Much appreciated.

Comment 14 errata-xmlrpc 2022-11-15 11:22:32 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 (setup bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:8386