I believe the first ubuntu package that had this change was
2:4.8.4+dfsg-2ubuntu1, in Cosmic (18.10), in August 2018.
** Changed in: samba (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This was fixed upstream via https://github.com/samba-
team/samba/commit/0e571054a61e9de69190ae023199d1670e097e88 by changing
the network dependency to network-online.target instead of just
network.target
** Tags added: network-online-ordering
--
You received this bug notification because you
Jorge, try this:
- show output of "ip a"
- in one terminal, run "tail -f /var/log/syslog"
- in another terminal, run "tail -f /var/log/samba/log*"
- in another terminal, run "sudo systemctl restart nmbd"
Check if nmbd starts up fine, or if the systemctl call hangs. If you
have no ipv4 network,
Jorge, try this:
- show output of "ip a"
- in one terminal, run "tail -f /var/log/syslog"
- in another terminal, run "tail -f /var/log/samba/log*"
- in another terminal, run "sudo systemctl restart nmbd"
Check if nmbd starts up fine, or if the systemctl call hangs. If you
have no ipv4 network,
Thank you, Andreas for providing the information and logging the bug.
However, in my case, I'm connected on a wired network so I don't
understand why I'm getting this bug.
Much thanks
Jorge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: triage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731502
Title:
nmbd starts fine with no interfaces, but doesn't notify systemd that
it started
To manage notifications about
