[Bug 1827924] Re: Panic or segfault in Samba

This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash. ** Bug watch added: Samba Bugzilla #13315

[Bug 1829822] Re: Panic or Segfault in Samba / Message comes for about a week several times a day

This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash. ** Bug watch added: Samba Bugzilla #13315

[Bug 1829772] Re: The Samba 'panic action'

This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash. ** Bug watch added: Samba Bugzilla #13315

[Bug 1829754] Re: Panic or segfault in Samba after migration to Ubuntu 16.04.6

This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash. ** Bug watch added: Samba Bugzilla #13315

[Bug 1829843] Re: Panic in Samba when creating session

This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash. ** Bug watch added: Samba Bugzilla #13315

[Bug 1829916] Re: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 31240 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. Below

This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash. ** Bug watch added: Samba Bugzilla #13315

[Bug 1823422] Re: heimdal ftbfs in disco

** Bug watch added: Debian Bug tracker #923930 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923930 ** Also affects: heimdal (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923930 Importance: Unknown Status: Unknown -- You received this bug notification

[Bug 1829380] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression)

This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.9~cloud6 --- qemu (1:2.8+dfsg-3ubuntu2.9~cloud6) xenial-ocata; urgency=medium . * SECURITY UPDATE: Add support for exposing md-clear functionality to guests - d/p/ubuntu/enable-md-clear.patch -

[Bug 1829380] Update Released

The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we

[Bug 1829484] Re: krb5-multidev dependency broken with ESM Trusty Repo

Thanks for getting back to us! No need to be sorry. I'll mark this bug as invalid then. If new information arises that could indicate this was something else, feel free to reopen the bug. ** Changed in: krb5 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification