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?



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

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.

  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

Status in openssh package in Ubuntu:

Bug description:
  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.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to