Bug 2049089 - Installation of non-existing package offered by bash fails on pressing "y"
Summary: Installation of non-existing package offered by bash fails on pressing "y"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: PackageKit
Version: CentOS Stream
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-01 14:25 UTC by Ravi
Modified: 2023-08-01 07:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-01 07:28:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-110536 0 None None None 2022-02-01 14:32:16 UTC

Description Ravi 2022-02-01 14:25:37 UTC
Description of problem:
I tried to open "xterm", but as the package was not installed, so I got an error, and an offer to install it by pressing "y", but when I press "y", I get an error command not found.


Version-Release number of selected component (if applicable):


How reproducible:
[root@localhost ~]# bash: xterm: command not found...

[root@localhost ~]# Install package 'xterm' to provide command 'xterm'? [N/y] y
bash: y: command not found...

[1]+  Stopped                 xterm

[1]+  Stopped                 xterm



Actual results:
bash: y: command not found...


Expected results:
"xterm" package should be installed.

Additional info:

Comment 1 Siteshwar Vashisht 2022-05-19 07:27:39 UTC
It's not a bug in bash and this message is coming from PackageKit.

Comment 3 RHEL Program Management 2023-08-01 07:28:07 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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