Your message dated Fri, 15 Feb 2019 14:40:14 +0100
with message-id 
<CAFX5sbzVR6v7Pk2jM+nQbLv=qd5rmzd5khosz0bpz2+aw97...@mail.gmail.com>
and subject line Closing
has caused the Debian Bug report #841676,
regarding samba: Samba segfaults for unknown reason
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.)


-- 
841676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841676
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:4.2.10+dfsg-0+deb8u3
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   Normal usage from a Windows client. When navigating into a SMB directory,
   client gets error message "permission denied" or similar. Must restart smb
   deamons on server to recover.
   * 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.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages samba depends on:
ii  adduser                              3.113+nmu3
ii  dpkg                                 1.17.27
ii  libbsd0                              0.7.0-2
ii  libc6                                2.19-18+deb8u6
ii  libhdb9-heimdal [heimdal-hdb-api-8]  1.6~rc2+dfsg-9
ii  libldb1                              2:1.1.20-0+deb8u1
ii  libpam-modules                       1.1.8-3.1+deb8u1+b1
ii  libpam-runtime                       1.1.8-3.1+deb8u1
ii  libpopt0                             1.16-10
ii  libpython2.7                         2.7.9-2+deb8u1
ii  libtalloc2                           2.1.2-0+deb8u1
ii  libtdb1                              1.3.6-0+deb8u1
ii  libtevent0                           0.9.25-0+deb8u1
ii  lsb-base                             4.1+Debian13+nmu1
ii  multiarch-support                    2.19-18+deb8u6
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.2.10+dfsg-0+deb8u3
pn  python2.7:any                        <none>
ii  samba-common                         2:4.2.10+dfsg-0+deb8u3
ii  samba-common-bin                     2:4.2.10+dfsg-0+deb8u3
ii  samba-dsdb-modules                   2:4.2.10+dfsg-0+deb8u3
ii  samba-libs                           2:4.2.10+dfsg-0+deb8u3
ii  tdb-tools                            1.3.6-0+deb8u1
ii  update-inetd                         4.43

Versions of packages samba recommends:
ii  attr               1:2.4.47-2
ii  logrotate          3.8.7-1+b1
ii  samba-vfs-modules  2:4.2.10+dfsg-0+deb8u3

Versions of packages samba suggests:
pn  bind9          <none>
pn  bind9utils     <none>
pn  ctdb           <none>
pn  ldb-tools      <none>
ii  ntp            1:4.2.6.p5+dfsg-7+deb8u2
pn  smbldap-tools  <none>
pn  winbind        <none>

-- debconf information:
  samba-common/title:
  samba/run_mode: daemons

--- End Message ---
--- Begin Message ---
Hi,

I'm closing this bug. It lacks any useful info.

Regards

-- 
Mathieu Parent

--- End Message ---

Reply via email to