Hi,
Thanks for your hint Peter Palensky to roll back the installation :D
With this tip I stripped down that the bug depends on the samba upgrade
from 2:4.1.17+dfsg-2+deb8u2 to 2:4.2.10+dfsg-0+deb8u2
With following state everything works as expected:
apt list --upgradable
Listing...
libldb1/stable 2:1.1.20-0+deb8u1 amd64 [upgradable from: 2:1.1.17-2+deb8u1]
libsmbclient/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
libwbclient0/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
python-ldb/stable 2:1.1.20-0+deb8u1 amd64 [upgradable from: 2:1.1.17-2+deb8u1]
python-samba/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
samba/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
samba-common/stable 2:4.2.10+dfsg-0+deb8u2 all [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
samba-common-bin/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
samba-dsdb-modules/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
samba-libs/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
samba-vfs-modules/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
smbclient/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
tdb-tools/stable 1.3.6-0+deb8u1 amd64 [upgradable from: 1.3.1-1]
winbind/stable 2:4.2.10+dfsg-0+deb8u2 amd64 [upgradable from:
2:4.1.17+dfsg-2+deb8u2]
after performing this upgrade the bug appears. Rolling back to this state
everything works ok.
Cheers
Ulli
