Bug 1814181 - f32 toolbox container always display "bash: /usr/libexec/vte-urlencode-cwd: No such file or directory"
Summary: f32 toolbox container always display "bash: /usr/libexec/vte-urlencode-cwd: N...
Keywords:
Status: CLOSED DUPLICATE of bug 1815769
Alias: None
Product: Fedora Container Images
Classification: Fedora
Component: fedora-toolbox
Version: 32
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-17 09:45 UTC by Junjie Yuan
Modified: 2020-03-23 07:52 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-23 07:52:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers toolbox issues 390 0 None open bash: /usr/libexec/vte-urlencode-cwd: No such file or directory 2020-03-23 07:48:56 UTC

Description Junjie Yuan 2020-03-17 09:45:39 UTC
Description of problem:
f32 toolbox container always display "bash: /usr/libexec/vte-urlencode-cwd: No such file or directory".
When using "podman container exec -it fedora-toolbox-32" (as root), this prompt will disappear.

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

toolbox-0.0.18-2.fc32.noarch
podman-1.8.0-5.fc32.x86_64

How reproducible:


Steps to Reproduce:
1.toolbox create (f32 container)
2.toolbox enter
3.do anything

Actual results:
Always display "bash: /usr/libexec/vte-urlencode-cwd: No such file or directory
"

Expected results:
Don't display "bash: /usr/libexec/vte-urlencode-cwd: No such file or directory
"

Additional info:
OS: fedora silverblue 32.20200316.n.0
REPOSITORY                                      TAG      IMAGE ID       CREATED       SIZE
registry.fedoraproject.org/f32/fedora-toolbox   32       f7cf4b593fc1   5 days ago    360 MB

Comment 1 Junjie Yuan 2020-03-23 07:52:19 UTC

*** This bug has been marked as a duplicate of bug 1815769 ***


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