Your message dated Tue, 15 Nov 2022 11:46:59 +0300 with message-id <[email protected]> and subject line Re: samba: Panic or segfault in Samba - smbd core generated has caused the Debian Bug report #808129, regarding samba: Panic or segfault in Samba - smbd core generated to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 808129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808129 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: samba Version: 2:4.1.17+dfsg-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.26 ii libasn1-8-heimdal 1.6~rc2+dfsg-9 ii libbsd0 0.7.0-2 ii libc6 2.19-18+deb8u1 ii libcomerr2 1.42.12-1.1 ii libhdb9-heimdal [heimdal-hdb-api-8] 1.6~rc2+dfsg-9 ii libkdc2-heimdal 1.6~rc2+dfsg-9 ii libkrb5-26-heimdal 1.6~rc2+dfsg-9 ii libldb1 2:1.1.17-2 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpopt0 1.16-10 ii libpython2.7 2.7.9-2 ii libroken18-heimdal 1.6~rc2+dfsg-9 ii libtalloc2 2.1.1-2 ii libtdb1 1.3.1-1 ii libtevent0 0.9.21-1 ii lsb-base 4.1+Debian13+nmu1 ii multiarch-support 2.19-18+deb8u1 ii procps 2:3.3.9-9 ii python 2.7.9-1 ii python-dnspython 1.12.0-1 ii python-ntdb 1.0-5 ii python-samba 2:4.1.17+dfsg-2 pn python2.7:any <none> ii samba-common 2:4.1.17+dfsg-2 ii samba-common-bin 2:4.1.17+dfsg-2 ii samba-dsdb-modules 2:4.1.17+dfsg-2 ii samba-libs 2:4.1.17+dfsg-2 ii tdb-tools 1.3.1-1 ii update-inetd 4.43 Versions of packages samba recommends: pn attr <none> ii logrotate 3.8.7-1+b1 pn samba-vfs-modules <none> Versions of packages samba suggests: ii bind9 1:9.9.5.dfsg-9+deb8u4 ii bind9utils 1:9.9.5.dfsg-9+deb8u4 pn ctdb <none> pn ldb-tools <none> ii ntp 1:4.2.6.p5+dfsg-7+deb8u1 pn smbldap-tools <none> ii winbind 2:4.1.17+dfsg-2 -- debconf information: samba/run_mode: daemons samba-common/title: samba/generate_smbpasswd: true Core file available here https://filesender.anevia.com/filesender/download.php?vid=200ee7a1-ea89-c868-e388-00005ea62017
--- End Message ---
--- Begin Message ---On Wed, 16 Dec 2015 11:37:52 +0100 Damien Martins <[email protected]> wrote:Package: samba Version: 2:4.1.17+dfsg-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines ***Not a useful bug report - no information is filled in, no logs, no configs, no nothing. The core file is unavailable today too. And there has been a *lot* of various issues leading to core dumps fixed in samba since that time. Closing this bug report. Thanks, /mjt
--- End Message ---
