Comment 2 for bug 1776809

Thanks for filing this bug in Ubuntu.

From the logs:
Setting up winbind (2:4.7.6+dfsg~ubuntu-0ubuntu2) ...
Job for winbind.service failed because the control process exited with error code.
See "systemctl status winbind.service" and "journalctl -xe" for details.
invoke-rc.d: initscript winbind, action "restart" failed.
● winbind.service - Samba Winbind Daemon
   Loaded: loaded (/lib/systemd/system/winbind.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-06-10 08:43:06 -04; 33ms ago
     Docs: man:winbindd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 6229 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 6229 (code=exited, status=1/FAILURE)

jun 10 08:43:06 ubuntu-desktop systemd[1]: Starting Samba Winbind Daemon...
jun 10 08:43:06 ubuntu-desktop systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
jun 10 08:43:06 ubuntu-desktop systemd[1]: winbind.service: Failed with result 'exit-code'.
jun 10 08:43:06 ubuntu-desktop systemd[1]: Failed to start Samba Winbind Daemon.
dpkg: error processing package winbind (--configure):
 installed winbind package post-installation script subprocess returned error exit status 1

Unfortunately that doesn't tell why winbind failed to start, only that it did. Since there is no smb.conf attached to this bug, I can't check that it does not contain errors.

I suggest the following:
- inspect the logs in /var/log/samba/log* to see if they have more information about the problem. These logs were not attached to this bug so I can't check.
- inspect your smb.conf for syntax errors, specially around the winbind parameters. Or run the testparm utility to do some basic checks for you.

I will mark this bug as incomplete until more information becomes available. Thanks.