Hi Andreas, If for ANY reason winbind service is not startable APT will be broken - that's the regression this ticket must address. The samba-winbind package has introduced hard dependency on external systems during installation process. 1. systemd - a failure to start service will breaks apt package manager. 2. PDC/BDC - a timeout or connect reset breaks apt package manager. 3. Network availability There is no debate - the reactive manifesto is clear that samba-winbind should be designed per best practice. https://www.reactivemanifesto.org/glossary#Non-Blocking A non-blocking API to a resource allows the caller the option to do other work rather than be blocked waiting on the resource to become available. https://www.reactivemanifesto.org/glossary#Message-Driven Responding to the failure of a component in order to restore its proper function, on the other hand, requires a treatment of these failures that is not tied to ephemeral client requests, but that responds to the overall component health state Please fix samba-winbind package to send non-blocking request systemd start winbind. Breaking apt is irresponsible (and legally unwise I imagine). Start winbind service in not-blocking fashion so system can continue to function. best regards, Noel On Mon, Mar 11, 2019 at 8:50 PM Andreas Hasenack