Your message dated Tue, 19 Jun 2018 21:45:55 +0200 with message-id <CAFX5sbymnMvRvP5+UNWhDy=THveJfuq=5fhj+acp9arhib+...@mail.gmail.com> and subject line Closing wheezy only bugs has caused the Debian Bug report #807775, regarding samba: Panic or segfault in Samba 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.) -- 807775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807775 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: samba Version: 2:4.1.21+dfsg-2+b2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Running samba * What exactly did you do (or not do) that was effective (or ineffective)? Ran samba * What was the outcome of this action? The below e-mail was sent to me * What outcome did you expect instead? No segfaults *** End of the template - remove these template lines *** The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 26441 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occurred. The Samba log files may contain additional information about the problem. If the problem persists, you are encouraged to first install the samba-dbg package, which contains the debugging symbols for the Samba binaries. Then submit the provided information as a bug report to Debian. For information about the procedure for submitting bug reports, please see http://www.debian.org/Bugs/Reporting or the reportbug(1) manual page. To enable execution of this file add add-auto-load-safe-path /lib/x86_64-linux-gnu/libthread_db-1.0.so line to your configuration file "$HOME/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "$HOME/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" __strftime_internal (s=<optimized out>, maxsize=<error reading variable: Cannot access memory at address 0xffffffffffffff29>, format=<optimized out>, tp=<error reading variable: Cannot access memory at address 0xffffffffffffff11>, tzset_called=<error reading variable: Cannot access memory at address 0xfffffffffffffef1>, loc=<error reading variable: Cannot access memory at address 0xffffffffffffff09>) at strftime_l.c:1407 #0 __strftime_internal (s=<optimized out>, maxsize=<error reading variable: Cannot access memory at address 0xffffffffffffff29>, format=<optimized out>, tp=<error reading variable: Cannot access memory at address 0xffffffffffffff11>, tzset_called=<error reading variable: Cannot access memory at address 0xfffffffffffffef1>, loc=<error reading variable: Cannot access memory at address 0xffffffffffffff09>) at strftime_l.c:1407 Backtrace stopped: Cannot access memory at address 0x9 A debugging session is active. Inferior 1 [process 26441] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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.18.3 ii libasn1-8-heimdal 1.6~rc2+dfsg-10 ii libbsd0 0.8.0-2 ii libc6 2.21-4 ii libcomerr2 1.42.13-1 ii libhdb9-heimdal [heimdal-hdb-api-8] 1.6~rc2+dfsg-10 ii libkdc2-heimdal 1.6~rc2+dfsg-10 ii libkrb5-26-heimdal 1.6~rc2+dfsg-10 ii libldb1 2:1.1.23-1 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.11-2 ii libroken18-heimdal 1.6~rc2+dfsg-10 ii libtalloc2 2.1.5-1 ii libtdb1 1.3.8-1 ii libtevent0 0.9.26-3 ii lsb-base 9.20150917 ii procps 2:3.3.10-4+b1 ii python 2.7.11-1 ii python-dnspython 1.12.0-1 ii python-ntdb 1.0-8 ii python-samba 2:4.1.21+dfsg-2+b2 pn python2.7:any <none> ii samba-common 2:4.1.21+dfsg-2 ii samba-common-bin 2:4.1.21+dfsg-2+b2 ii samba-dsdb-modules 2:4.1.21+dfsg-2+b2 ii samba-libs 2:4.1.21+dfsg-2+b2 ii tdb-tools 1.3.8-1 ii update-inetd 4.43 Versions of packages samba recommends: ii attr 1:2.4.47-2 ii logrotate 3.8.7-2 ii samba-vfs-modules 2:4.1.21+dfsg-2+b2 Versions of packages samba suggests: pn bind9 <none> ii bind9utils 1:9.9.5.dfsg-12+b1 pn ctdb <none> pn ldb-tools <none> pn ntp <none> pn smbldap-tools <none> pn winbind <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi, I'm closing bugs that are wheezy only (EOL). Please reopen if you are still experiencing it in newer releases. Regards -- Mathieu Parent NB: Query on UDD: select id, severity, title from bugs where bugs.source='samba' and not affects_unstable and not affects_testing and not affects_stable and not affects_oldstable and status!='done' ORDER BY id; #893689 was removed from the list.
--- End Message ---
