Hi Joe, the initial bug contains no journal log or systemctl status of the failing service after install. On the initial report per TerminalLog it seems smb itself failed:
Aug 15 09:11:35 Thinkpad smbd[17311]: STATUS=daemon 'smbd' finished starting up and ready to serve connections Aug 15 09:11:37 Thinkpad systemd[1]: smbd.service: Failed with result 'timeout This is odd to me, it first reports to be started and happy, to then fail with a timeout. The latter update in comment #3 with the failing samba-ad-dc.service seems to be the service that fails after downgrade right? I've so far seen this particular issue on e.g. [1], but other than retrying there was nothing there that could be reused here. @Andreas - do you have a better samba-idea what to look for? @Joe - is this reproducible? If so can you after upgrade show the "systemctl status" of the failed smbd service and also add the "journalctl -xe" output including other things happening around that time? [1]: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1677329/comments/21 ** Changed in: samba (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787210 Title: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1787210/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
