Oh I assumed this was running s390x VM on s390x Host.
@Ryan - is this s390x emulation on a non-s390x host?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that the issue may be in qemu in 22.04. A "real" s390x
running 22.04 does not have this issue and the same installation image
does not have this issue running on Windows 11, qemu version 7.0.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I only have one s390x guest and adding another would be painful due to
the slowness of its emulation :) but I have just tried removing all of
/etc/ssh and reinstalling openssh-client/openssh-server, same crash.
To be clear, this is only happening on my s390x guest. I have a few
other non-x86
@Ryan - Before going deeper since I read
"readconf.c:read_config_file_depth" in there. Does the same happen on a
fresh Jammy guest that has all-default config files? Or only to this
particular guest that you have?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
(gdb) bt
#0 __GI__IO_default_xsputn (n=, data=,
f=) at libioP.h:947
#1 __GI__IO_default_xsputn (f=0x3ffcbc7c2e8, data=,
n=2929360903402) at genops.c:370
#2 0x03ffa6c7896c in outstring_func (done=11, length=2929360903402,
string=0x2aa0b841cea <__func__.3.lto_priv.14>
Hi,
for comparison on another system I've taken a Host (was impish before upgrade)
and created guests with Xenial, Bionic, Focal, Jammy.
All worked fine at this stage - ssh login and health of guests/hosts was good.
Then I upgraded the Host to Jammy (as the reporter did).
Example of the simple
** Tags added: apport-crash need-amd64-retrace
** Tags removed: need-amd64-retrace
** Tags added: need-s390x-retrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970076
Title:
"User process
