Hello Michael, or anyone else affected, Accepted systemd into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.19 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1473800 Title: restarting logind during systemd update causes screen to lock Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Committed Bug description: When systemd is updated (through the update manager), the screen/session locks when processing the update. I've had this happen twice I think, and the only suspicious packages are the systemd ones. SRU INFORMATION: ================ - Fix from wily/xenial: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/diff/?id=b8c239 ; This follows other distributions like Fedora which never restarted logind on package upgrades. This just causes too much fallout from clients which listen to the D-Bus address and get confused when logind goes away and comes back. - Regression potential: This is harmless as long as we don't push an urgent fix to logind itself as an SRU. In this case we might need to re-add the restart on upgrade (with a version guard). This is unlikely/seldom, though. For this particular upgrade there is no regression potential as there are no logind changes (for the record, we've never had a logind SRU so far). - Test case: * Check "pidof systemd-logind" * Upgrade "systemd-services" and "libpam-systemd" to the -proposed version * The above upgrade will restart logind (as we can't retroactively fix the prerm of the old package) and "pidof systemd-logind" should now show a different pid. * sudo apt-get install --reinstall libpam-systemd → now "pidof systemd-logind" should be identical to the previous one, i. e. from now on upgrades of libpam-systemd do not restart logind any more. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 222-1ubuntu3 ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7 Uname: Linux 4.0.0-4-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 13 09:49:47 2015 InstallationDate: Installed on 2015-01-31 (162 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic root=UUID=4c827ac5-3a87-4443-86eb-a55dca9626ad ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A88X Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1473800/+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
