[Bug 1575056] Re: smbd crashed with SIGABRT in strlen()

2016-04-26 Thread Thomas A. F. Thorne
*** This bug is a duplicate of bug 1514766 *** https://bugs.launchpad.net/bugs/1514766 Is it safe for Apport to mark bugs as public when it decides they are a duplicate of another public bug? Does it do any checking of the SMBConf.txt to ensure there is no sensitive information in there or do

[Bug 1575056] Re: smbd crashed with SIGABRT in strlen()

2016-04-26 Thread Apport retracing service
*** This bug is a duplicate of bug 1514766 *** https://bugs.launchpad.net/bugs/1514766 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1514766, so is being marked as such.

[Bug 1575056] Re: smbd crashed with SIGABRT in strlen()

2016-04-26 Thread Thomas A. F. Thorne
*** This bug is a duplicate of bug 1514766 *** https://bugs.launchpad.net/bugs/1514766 I do not see anything sensitive in the SMBConf.txt so I think it is safe to mark this bug as not private. I'll wait to see what the re-trace brings out and then look into it. -- You received this bug noti