** Changed in: oem-priority
Status: In Progress => 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/1842651
Title:
Regression: after Uprade from
Ok working, my problem was not directly related to this bug. Sorry,
please forget my comment #20 and #21!
--
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/1842651
Title:
See my attachment please. System stuck on boot.
** Attachment added: "console detail on boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651/+attachment/5287976/+files/bug.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi,
After this update (237-3ubuntu10.29) on this morning (11 sept.) my system no
more booting!
Black screen after grub, select other kernel but nothing works. I suppose it is
linked with this update...
...
Failed to start Network Manager
Dependency failed for Network Manager Wait Online
...
237-3ubuntu10.29 - works for me (Ubuntu 18.04.3 LTS, 4.15.0-51-generic)
Thank you!
--
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/1842651
Title:
Regression: after Uprade
This bug was fixed in the package systemd - 240-6ubuntu5.7
---
systemd (240-6ubuntu5.7) disco; urgency=medium
* d/p/d/Revert-udev-network-device-renaming-immediately-give.patch:
- udev: add Revert-udev-network-device-renaming-immediately-give.patch back
Dropping this
This bug was fixed in the package systemd - 237-3ubuntu10.29
---
systemd (237-3ubuntu10.29) bionic; urgency=medium
* d/p/d/Revert-udev-network-device-renaming-immediately-give.patch:
- udev: add Revert-udev-network-device-renaming-immediately-give.patch back
Dropping this
@Rex and @Shih-Yuan, I believe Chris is planning to push this through
-security in his morning.
--
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/1842651
Title:
Regression:
** Changed in: oem-priority
Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)
--
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/1842651
Title:
Regression: after
Is there anything we can do to speed up the process? What would be the
next step to land the reverted version for the regression?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)
** Changed in: oem-priority
Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
> Please reject the packages that are currently in the unapproved queue.
Done
--
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/1842651
Title:
Regression: after Uprade from
I've uploaded the changes that were sponsored to proposed to
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa.
Please reject the packages that are currently in the unapproved queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
FYI, this broke me as well. I have an 18.04 multi-nic system that went
through several upgrades and was relying on /etc/udev/rules.d/70
-persistent-net.rules to give me predictable eth* names where each eth*
name was used as part of a bridge. The recent change regressed this
since non-existent
Rather than going through -proposed, it needs to go via one of our
security PPAs (which are built without -updates) and then copied across,
which is something I can do.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
@chrisccoulson - I sponsored the changes as per normal, so they're in
the queue for -proposed in bionic and disco. Can I upload to the
security pocket? Does that just require debian/changelog to be changed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
If this change is being reverted, it needs to be done via the security
pocket rather than proposed, as Tuesday's security update was based on
the version with this regression.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/372334
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
[Impact]
- * Many server users upgraded from previous Ubuntu LTS series, such as
+ * Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
- * Because there is
** Description changed:
- Since the latest update from udev_237-3ubuntu10.25 and
- systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
- systemd_237-3ubuntu10.26 the renaming of network interfaces by
- /etc/udev/rules/70-persistent-network.rules does not work.
+ [Impact]
+
+ * Many server
** Merge proposal linked:
https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/372318
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)
** Changed in: oem-priority
Assignee: Che Cheng (cktenn) => Shih-Yuan Lee (fourdollars)
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: oem-priority
** Changed in: oem-priority
Status: In Progress => Confirmed
--
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/1842651
Title:
Regression: after Uprade from
** Changed in: oem-priority
Status: New => In Progress
--
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/1842651
Title:
Regression: after Uprade from
The user will have a 70-persistent-net.rules generated by
/lib/udev/write_net_rules, when they upgraded from 14.04/12.04 to newer
version. The server user may have the iptables rules or netowrk ip
setting based on the persistent interface name. This is critical.
The regression is introduced in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> Any reason you cannot move to new naming scheme?
Please remember that this report may represent a large number of
affected users, most of whom are absent from this discussion. We want to
avoid regressing stable release Ubuntu users as much as possible, and
this generally means that we cannot
A lot of dependencies and the new naming scheme is too unreliable because
multiple servers are being served. with 70-persistent-net.rules we can trust
the interfaces get the correct device name we need (until now).
If something like that is broken during a release change (18.04 to 19.04) it's
That patch has also been obsoleted in Debian recently, and upstream
systemd has no longer support 70-persistent-net.rules thing. Any reason
you cannot move to new naming scheme?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Same Problem with version .28!
--
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/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
** Tags added: oem-priority
--
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/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => Che Cheng (cktenn)
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
I had the same problem with 237-3ubuntu10.28 AND 237-3ubuntu10.26.
237-3ubuntu10.25 was the solution.
--
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/1842651
Title:
Neither .25 nor .26 are the most current systemd versions in bionic.
Can you please double check your version numbers?
Could you please try 237-3ubuntu10.28 and check if problem persists?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
34 matches
Mail list logo
