Hello Christian, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1805358 Title: autopkgtest boot-and-services fails on many architectures very often since systemd/239-7ubuntu12 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * Boot and services autopkgtest case has become flakey, especially on ppc64el but other architectures too. [Test Case] * Check that boot-and-services passes more reliably [Regression Potential] * this is a test change only [Other Info] * gdm3 used to start reliably, in nested qemu, with dummy xorg, but it doesn't anymore. Thus stop testing gdm3 coming up as part of the systemd autopkgtest. Mostly, because in realisty it's not that interesting to see if gdm3 works with dummy xorg, as we mostly care about gdm3 working on bare-metal with proper graphics cards intel/amd/nvidia/etc. I appreciate that some old known issues on 'upstream' are fixed. But looking at the current tests I see that often on amd64 (2/3 and very often on ppc64le (4/4 since ubuntu12 and 11/11 before that version). Looking at the list of people hitting retry and the list of packages blocked that seems an issue that must be checked. See current head of tests at: amd64: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/amd64 ppc64el: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/ppc64el One example log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20181126_074048_cb8d2@/log.gz Example of the error that one can see in the log: test_no_failed (__main__.ServicesTest) No failed units ... -------- journal for failed service user@118.service ----------- -- Logs begin at Tue 2018-10-30 09:54:39 UTC, end at Mon 2018-11-26 07:05:17 UTC. -- Nov 26 07:05:09 autopkgtest systemd[1]: Starting User Manager for UID 118... Nov 26 07:05:10 autopkgtest systemd[1292]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) Nov 26 07:05:10 autopkgtest systemd[1292]: Failed to fully start up daemon: Permission denied Nov 26 07:05:10 autopkgtest systemd[1]: user@118.service: Failed with result 'protocol'. Nov 26 07:05:10 autopkgtest systemd[1]: Failed to start User Manager for UID 118. FAIL ====================================================================== FAIL: test_no_failed (__main__.ServicesTest) No failed units ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.Xm5RBa/build.JSa/src/debian/tests/boot-and-services", line 62, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['user@118.service loaded failed failed User Manager for UID 118'] != [] First list contains 1 additional elements. First extra element 0: 'user@118.service loaded failed failed User Manager for UID 118' - ['user@118.service loaded failed failed User Manager for UID 118'] + [] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805358/+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
