sshd crashed with SIGSEGV in _IO_vfprintf_internal()

[msp3k]

sshd crashes several times a day with the following information:

ExecutablePath: /usr/sbin/sshd
Package: openssh-server 1:6.6p1-2ubuntu2.3
ProblemType: Crash
Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal()
Architecture: amd64
DistroRelease: Ubuntu 14.04

I've been reporting this bug for months now through apport-gtk, but there never seems to be an entry for it on launchpad. So just in case this isn't making it into the bug reports, for whatever reason, I'm reporting it manually here.

[Seth Arnold (seth-arnold)]

It may not be making its way to errors.ubuntu.com. If you've got the GUI installed, you can find a link to reported issues via the control panel, security & privacy, diagnostics --> "show previous reports". I didn't see any errors that matched _IO_vfprintf_internal(), though I did notice that the pam_winbind module was segfaulting a lot for someone...

Thanks

[msp3k (peek-nimbios)]

I tried following one of the links to ubuntu.com, but was told "Sorry,
you are not a member of a group that is allowed to see the data from
error reports."

If you think it's safe to do so, I can reply with the last few links.
Would it be safe to assume that they are listed in a newest-first order?

Thanks,

Michael

On 01/05/2016 09:17 PM, Seth Arnold wrote:
> It may not be making its way to errors.ubuntu.com. If you've got the GUI
> installed, you can find a link to reported issues via the control panel,
> security & privacy, diagnostics --> "show previous reports". I didn't
> see any errors that matched _IO_vfprintf_internal(), though I did notice
> that the pam_winbind module was segfaulting a lot for someone...
>
> Thanks
>

[Seth Arnold (seth-arnold)]

On Wed, Jan 06, 2016 at 02:07:59PM -0000, msp3k wrote:
> I tried following one of the links to ubuntu.com, but was told "Sorry,
> you are not a member of a group that is allowed to see the data from
> error reports."

Hmm, I thought you'd always be able to view your own reports.

> If you think it's safe to do so, I can reply with the last few links.
> Would it be safe to assume that they are listed in a newest-first order?

I believe it is safe; I don't recall seeing anything private in the other
reports but didn't want to risk it.. but if you've got URLs for your
reports, then they probably are making it to the error tracker. The thing
is, very few reports are -- you may be the only one gettnig these.

Thanks

[msp3k (peek-nimbios)]

I have not come across this bug yet in 16.04. It may have been fixed.

Michael

On 10/26/2016 06:08 PM, Joshua Powers wrote:
> ** Changed in: openssh (Ubuntu)
> Status: New => Incomplete
>

[Launchpad Janitor (janitor)]

[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]