** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1896614
Title:
Race condition when starting dbus services
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Bug description:
In certain scenarios, such as high load environments or when
"systemctl daemon-reload" runs at the same time a dbus service is
starting (e.g. systemd-logind), systemd is not able to track properly
when the service has started, keeping the job 'running' forever.
The issue appears when systemd runs the "AddMatch" dbus method call to
track the service's "NameOwnerChange" once it has already ran. A
working instance would look like this:
https://pastebin.ubuntu.com/p/868J6WBRQx/
A failing instance would be:
https://pastebin.ubuntu.com/p/HhJZ4p8dT5/
I've been able to reproduce the issue on Bionic (237-3ubuntu10.42)
running:
sudo systemctl daemon-reload & sudo systemctl restart systemd-logind
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
