[Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-12-26 Thread Launchpad Bug Tracker
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-10-27 Thread msp3k
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
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-10-26 Thread Joshua Powers
** 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.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-06 Thread msp3k
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
>

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-06 Thread msp3k
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
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-06 Thread Seth Arnold
On Wed, Jan 06, 2016 at 02:07:59PM -, 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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-06 Thread Seth Arnold
On Wed, Jan 06, 2016 at 02:07:59PM -, 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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-05 Thread 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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()

2016-01-05 Thread 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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1530914

Title:
  sshd crashed with SIGSEGV in _IO_vfprintf_internal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs