search for: calledprocesserror

the script works... root at probe28:~# cat test.dat dn: CN=userxxxx,OU=Users,OU=xxxxx,OU=Organizations,DC=xxxxx,DC=xxxxx proxyAddresses: SMTP:xxxxx.xxxxx at xxxxx.org objectGUID: 637f4e70-8c1e-4e89-a6fc-82d525e584f2 pwdLastSet: 0 objectSid: S-1-5-21-1608159440-4144762864-1017073214-27184 sAMAccountName: userxxxx mail: xxxxx.xxxxx at xxxxx.xxxxx userAccountControl: 514 virtualClearTextUTF8::

...nicate(input)[0], encoding = > 'utf-8') > > After that 'subprocess.py' is called and the error seems to coming > from > there. Samba doesn't import all of 'subprocess', it only does this: > from > subprocess import Popen, PIPE, STDOUT, check_call, CalledProcessError > > The error output goes on to do this: > > File "/usr/lib/python3.6/subprocess.py", line 863, in communicate > stdout, stderr = self._communicate(input, endtime, timeout) > File "/usr/lib/python3.6/subprocess.py", line 1519, in > _communicate...

Hi, I have just tagged the 10.0.1-rc1 release. Testers can begin testing and uploading binaries. If you still want to get a fix into the 10.0.1 release, you still have about a month to get your fix in. To request a patch be backported to the release/10.x branch, file a bug and mark it as a blocker of the release-10.0.1 meta bug. -Tom