[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 231-9ubuntu1 --- systemd (231-9ubuntu1) yakkety; urgency=medium * debian/gbp.conf: Switch to yakkety branch * unit: sent change signal before removing the unit if necessary (LP: #1632964) * networkd: Fix assertion crash on adding

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu12 --- systemd (229-4ubuntu12) xenial; urgency=medium * unit: sent change signal before removing the unit if necessary (LP: #1632964) * networkd: Fix assertion crash on adding VTI with IPv6 addresses (LP: #1633274)

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-30 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 231-10 --- systemd (231-10) unstable; urgency=medium [ Martin Pitt ] * systemctl: Add --wait option to wait until started units terminate again. * nss-resolve: return NOTFOUND instead of UNAVAIL on resolution errors. This makes it

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-26 Thread Martin Pitt
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632964 Title: Regression: systemd does not send all queued DBus Signals when a

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-26 Thread seahawk1986
Hello, both systemd packages in the -proposed repository for xenial (229-4ubuntu12) and yakkety (231-9ubuntu1) are sending all the DBus signals I need to track unit state changes, thank you very much for fixing this regression. -- You received this bug notification because you are a member of

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-26 Thread Andy Whitcroft
Hello seahawk1986, or anyone else affected, Accepted systemd into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/231-9ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-26 Thread Chris J Arges
Hello seahawk1986, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-26 Thread Martin Pitt
** Description changed: Since the penultimate systemd package update in september (229-4ubuntu8) systemd does not send the remaining queued DBus signals (e.g. PropertiesChanged) when a unit's state changes to inactive. Sending those signals has been working since the release of Ubuntu

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-16 Thread seahawk1986
I have been able to reproduce those missing signals most reliably within a systemd user session (for the system session it works most of the time): Steps to reproduce missing dbus signals with Ubuntu 16.10 Desktop: Create a ~/.config/systemd/user/terminal.service with this content: [Unit]

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-13 Thread Martin Pitt
So I suppose this got broken as a subtle side effect from https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h =ubuntu-xenial=5c429176 (bug 1529079). Do you have a reproducer for this that we can use to verify the fix? ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-13 Thread Martin Pitt
Setting to "incomplete" as this still needs a reproducer for SRU verification. ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-13 Thread Martin Pitt
Backported to xenial for SRU: https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?h=ubuntu-xenial=9b6838e4f ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-13 Thread Martin Pitt
Backported to yakkety branch for SRU: https://anonscm.debian.org/cgit /pkg-systemd/systemd.git/commit/?h=ubuntu-yakkety=51fedb3eed0 ** Changed in: systemd (Ubuntu Yakkety) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-13 Thread Martin Pitt
I cherry-picked the patch into Debian master, which will sync into z-series: https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=d261af7f0 ** Changed in: systemd (Ubuntu Z-series) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Z-series) Assignee:

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-10-13 Thread Ubuntu Foundations Team Bug Bot
The attachment "Patch for systemd-229-4ubuntu10" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned