OK I ran the command and this is what happened:
trevor@trevor-laptop:~$ sudo /etc/init.d/smbd start
[ ok ] Starting smbd (via systemctl): smbd.service.
and very little if any entries in /var/log/samba or /var/crash
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Before I run the command I discovered an existing file in /var/crash
that may be relevant to the original crash. I have attached it to this
post
** Attachment added: "samba.0.crash"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1676153/+attachment/4849892/+files/samba.0.crash
--
You
Happy to do this but I'm no expert so I'd be grateful if you could tell
me where the logs will be located and how I provide them correctly. Also
I am assuming that I can just go a do it from a terminal straight away
rather than waiting for the crash to occur? Correct?
--
You received this bug
Public bug reported:
May be the same as #1676018 but this crash occurred on a 32-bit CPU
during a routine update
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.5
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic
*** This bug is a duplicate of bug 1098334 ***
https://bugs.launchpad.net/bugs/1098334
I have been experiencing this bug (only after upgrade to saucy) and
mostly in Firefox but also in gnome terminal. Unlike the duplicate bug
#1098334 there is no flickering involved. The corrupted character
