Hello Brian, or anyone else affected,

Accepted systemd into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/systemd/208-8ubuntu8.2
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 Utopic)
       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/1400203

Title:
  libsystemd-login sd_login_monitor_new not working

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  The systemd login monitoring library (API: sd_login_monitor_new(3)) is not
  functional in Utopic. This library is a dependency in NetworkManager, for
  tracking user sessions. As a result, my laptop does not reconnect to
  the network after a suspend/resume cycle.

  There was a patch to fix this in the older, Trusty Tahr version of systemd
  
(http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/systemd/trusty/view/head:/debian/patches/login-monitor-no-machine.patch).
  The patch isn't in the utopic systemd (208-8ubuntu8).

  This was discovered in a Gnome Fallback session, but I think this KDE issue
  may be the same thing: https://bugs.kde.org/show_bug.cgi?id=340568
  Note: This behavior is only seen when "All users may connect to this
  network" is un-selected in NetworkManager.
  NOTE: in order to get a fully working network, I also had to make a
  change to the upstart script, see:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205

  [Test Case]
  A short C program to demonstrate sd_login_monitor_new is attached to the
  bug, to demonstrate whether sd_login_monitor_new() is working. 

  To do an end-to-end test, you can stop NetworkManager, re-run it with
  "NetworkManager --no-daemon", and look for the "Error getting login
  monitor:" error message.

  [Regression Potential]
  Fixing this simply means applying a patch which shipped along with
  Trusty Tahr's systemd. Since it was widely used already, adding it to
  Utopic does not appear overly risky.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+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

Reply via email to