I suggest you open a new bug with your crash info. This one is too old.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/515048
Title:
nmbd crashed with SIGSEGV in _IO_vfprintf_internal()
T
User is no longer able to reproduce.
chuck
** Changed in: samba (Ubuntu)
Status: Confirmed => Invalid
--
nmbd crashed with SIGSEGV in _IO_vfprintf_internal()
https://bugs.launchpad.net/bugs/515048
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: samba (Ubuntu)
Status: Incomplete => Confirmed
--
nmbd crashed with SIGSEGV in _IO_vfprintf_internal()
https://bugs.launchpad.net/bugs/515048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubunt
i have no clue as to reproducing it; it happened once and hasn't since
that time, i reported it in case the apport report might be
useful/obvious
--
nmbd crashed with SIGSEGV in _IO_vfprintf_internal()
https://bugs.launchpad.net/bugs/515048
You received this bug notification because you are a mem
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
** Changed
** Visibility changed to: Public
--
nmbd crashed with SIGSEGV in _IO_vfprintf_internal()
https://bugs.launchpad.net/bugs/515048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-se
