[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (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/1756202
T
Please open a separate bug, @ppedrotti. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756202
Title:
nmbd crashed with SIGABRT in dbghdrclass()
To manage notifications about this bug go to:
I can not upload any file to this bug report, I have been trying to do
that all the week without any success. I am not sure if I have an issue
or if there is an issue with the website. As soon as the problem gets
fixed I will upload the crash file in /var/crash.
--
You received this bug notificat
I didn't notice that the crash signal was different. Everything in the
logs uploaded by OP looked the same as mine so I didn't upload mine. If
my bug is different from the one reported initially I'll open another
one and reupload everything there.
--
You received this bug notification because you
@ppedrotti, you seem to have a different crash. I see a signal 7
(sigbus?).
Would you be able to attach the crash file from /var/crash?
** Changed in: samba (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I also have this issue on Ubuntu 18.04. When nmbd crashes it always
happens after the system resumes from suspension or hibernation. I
didn't notice any crashes on any other ocasion.
** Attachment added: "log.nmbd"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1756202/+attachment/514204
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (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/1756202
T
This is a rather generic error in nmbd/smbd as this is just the way it aborts.
>From the stack so far I can't derive any insight yet.
I looked but found no bug being exactly the same, just many others where the
SIG_ABRT hit.
Is that issue reproducible?
If so how?
In general attaching the nmbd.lo
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
