Your message dated Tue, 15 Nov 2022 11:44:27 +0300
with message-id <[email protected]>
and subject line Re: Bug#784142: it's getting worse
has caused the Debian Bug report #784142,
regarding samba: One share is getting access denied after wheezy-jessie upgrade.
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.)
--
784142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784142
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:4.1.17+dfsg-2
Severity: normal
Dear Maintainer,
After an upgrade from wheezy to jessie, one particular samba share is being
denied
access when accessed from windows computers on the LAN. This happens everytime
a windows machine is resumed from suspend/hibernate mode. It's 100%
reproducible.
All windows 7 machines are affected. Rebooting the windows machine fixes the
issue, until that computer is suspended again.
All other shares are accessible. Only one single share presents this issue.
That share can still be accessed locally with smbclient.
All has been working for years until that jessie upgrade.
Impossible to downgrade samba to oldstable: too many packages depends on
samba4: I tried that.
Result of this issue: I must now shut down every windows 7 computer instead
of suspending them.
Also if they automatically went into suspend mode after inactivity, I must
restart them after resume to re-enable read access to that share.
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable'), (100, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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.25
ii libasn1-8-heimdal 1.6~rc2+dfsg-9
ii libbsd0 0.7.0-2
ii libc6 2.19-18
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
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:
ii attr 1:2.4.47-2
ii logrotate 3.8.7-1+b1
ii samba-vfs-modules 2:4.1.17+dfsg-2
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
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
--- End Message ---
--- Begin Message ---
Version: 2:4.3.0+dfsg-1
On Thu, 07 Jan 2016 20:08:06 +1300 Andrew Bartlett <[email protected]> wrote:
I suggest trying the Samba 4.3 packages from unstable or a source buildand if
it still reproduces, then reporting this upstream with level 10 logs etc. That
will give us the best chance of working out what is going on.
It's been 6 years and there was no information and no activity there.
Assuming this has been fixed in 4.3 version, or maybe in a later
version.
If you think this is incorrect and the issue still present in current
version of samba (4.16 or 4.17), please feel free to reopen this
bug report and provide information requested.
Thanks,
/mjt
--- End Message ---
