On Tue, 2 Dec 2025 09:03:51 -0500
Stephen Gallagher <[email protected]> wrote:

> On Tue, Dec 2, 2025 at 3:20 AM Dan Horák <[email protected]> wrote:
> >
> > On Mon, 1 Dec 2025 20:40:29 -0500
> > Stephen Gallagher <[email protected]> wrote:
> >
> > > On Wed, Aug 13, 2025 at 3:19 AM Marián Konček <[email protected]> wrote:
> > > >
> > > > When I run `podman run --arch s390x --rm -it fedora:rawhide` as well as
> > > > `mock -r fedora-rawhide-s390x --shell`, the shell prompt is missing but
> > > > the shell is still working.
> > > >
> > > > On F41 shell looks correct.
> > > >
> > > > This seems like a bug somewhere in the container.
> > > >
> > >
> > > Just wanted to bring this back up. It appears that something is broken
> > > on the fedora:43-s390x and fedora:44-s390x containers, but
> > > fedora:42-s390x works just fine.
> > >
> > > I'm trying to debug an issue on one of my projects that is appearing
> > > only on s390x and it's certainly not easy when the shell is broken :(
> > >
> > > I think it's related to the TTY handling, because it doesn't matter
> > > what shell is in use.
> >
> > hmm, I wonder if it could be related to the termios changes in glibc
> > 2.42 that landed in F-43. But there have been reports about apps
> > accessing serial ports being broken so far. There is an issue with
> > screen (not echoing typed text or similar) that I still need to look at,
> > but that came with the rebase to 5.0 in F-42 I believe.
> >
> > Stephen, do you have more details? Because on a F-42 host I am getting
> > a working shell prompt when running
> > "podman run --rm -it fedora:43-s390x" (same with fedora:44-s390x)
> >
> 
> 
> Hmm, I suppose it's possible that the host might matter as well. I'm
> running podman-5.7.0-1.fc43.x86_64 and the following commands (the
> `ls` is typed in by me and followed by <enter>`):

ah, so it's cross-arch (non-native) use case as the original report. I
have tried that natively.

I have rechecked your
podman run --rm --tty --interactive  fedora:43-s390x  /usr/bin/bash
running from Rawhide/s390x and it works as expected. So it's an
emulation issue (incorrect parameter translation?) most likely ...

BTW s390x systems are easily available from (internal) Testing Farm.


                Dan
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to