[Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working

[Brian Bloniarz]

Apologies for the delay, I updated the bug description with a
justification for SRU; let me know if there's anything else I can do to
help.

** Description changed:

- There is a C API in libsystemd-login for receiving notifications, see
- sd_login_monitor_new(3). It is not working in the Utopic version of
- systemd, because it attempts to access /run/systemd/machines which does
- not exist on utopic.
+ [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.
  
- I see 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).
+ 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).
  
- I tracked down an issue in NetworkManager which I believe was due to
- this issue. Attached is a C program to demonstrate.
+ 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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
  In Progress

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