[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
Based on this bug: https://bugs.launchpad.net/ubuntu/+source/update- manager/+bug/1376612 , this is not a regression; the same error occurs in earlier versions of the package too. ** Tags removed: verification-failed verification-needed ** Tags added: verification-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/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
[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
Verified the sd-test.c program, using systemd 208-8ubuntu8.2 in utopic- proposed. -- 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
[Touch-packages] [Bug 1408747] Re: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1376612 *** https://bugs.launchpad.net/bugs/1376612 ** This bug has been marked a duplicate of bug 1376612 package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: pam-auth-update dies in debconf -- 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/1408747 Title: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: Installed with gui updater ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpam-systemd:amd64 208-8ubuntu8.2 Uname: Linux 3.16.6-031606-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Thu Jan 8 13:12:51 2015 DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu8.2:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2013-09-18 (476 days ago) InstallationMedia: This SourcePackage: systemd Title: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1408747/+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
[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
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 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: 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 -- 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
[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
@mark: I put up a PPA with the fix, if you'd like to test that: https://launchpad.net/~brianbloniarz/+archive/ubuntu/systemd-1400203 -- 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: In Progress Bug description: 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. 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). I tracked down an issue in NetworkManager which I believe was due to this issue. Attached is a C program to demonstrate. 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
[Touch-packages] [Bug 1400205] Re: network-manager may start before libsystemd-logind
Yes - have a look at the network-manager-logind.patch that's attached to this bug. That can be applied directly to /etc/init/network- manager.conf, it just adds a pre-start section to the init script. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1400205 Title: network-manager may start before libsystemd-logind Status in network-manager package in Ubuntu: Confirmed Bug description: When NetworkManager starts, it requests systemd login-monitor notifications through the libsystemd-login sd_login_monitor_new(3) API. This API will fail if the systemd-logind service has not been started, since it directly accesses directories in /run/systemd. As far as I can tell, systemd-logind in Utopic is started on-demand (through DBUS service activation). So, there's no guarantee that it has been started at the point during boot when NetworkMonitor is started. I attached a patch to upstart .conf file with one way to fix it -- it contacts the DBUS logind API within pre-start to ensure it has been started. NOTE: you will not see the error in syslog -- NetworkManager logs it to stderr which is /dev/null. If you enable --no-daemon on NetworkManager, the error (sd_login_monitor_new failed) should get logged to /var/log/upstart/network-manager.log. NOTE: even with this fix, I saw that sd_login_monitor_new failed -- I believe that's a bug in Utopic's systemd (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203). I had to patch both to resolve a suspend/resume issue for me. Seen on: Ubuntu 14.10 NetworkManager 0.9.8.8-0ubuntu28 libsystemd-login0 208-8ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205/+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
Re: [Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
Sure will add description ASAP, and yes I'm happy to test. On Dec 23, 2014 6:45 AM, Martin Pitt martin.p...@ubuntu.com wrote: Can you please add a proper impact description that justifies that SRU, and would you be willing to test the update in -proposed? -- You received this bug notification because you are subscribed to the bug report. 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: Triaged Bug description: 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. 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). I tracked down an issue in NetworkManager which I believe was due to this issue. Attached is a C program to demonstrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+subscriptions -- 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: In Progress Bug description: 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. 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). I tracked down an issue in NetworkManager which I believe was due to this issue. Attached is a C program to demonstrate. 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
[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
Whoops, done! ** Attachment added: Demonstration of problem https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+attachment/4282552/+files/sd-test.c -- 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: New Bug description: 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. 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). I tracked down an issue in NetworkManager which I believe was due to this issue. Attached is a C program to demonstrate. 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
[Touch-packages] [Bug 1400203] [NEW] libsystemd-login sd_login_monitor_new not working
Public bug reported: 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. 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). I tracked down an issue in NetworkManager which I believe was due to this issue. Attached is a C program to demonstrate. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** 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. 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). - I tracked down an issue in gnome-session which I believe was due to this - issue. Attached is a C program to demonstrate. + I tracked down an issue in NetworkManager which I believe was due to + this issue. Attached is a C program to demonstrate. -- 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: New Bug description: 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. 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). I tracked down an issue in NetworkManager which I believe was due to this issue. Attached is a C program to demonstrate. 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
[Touch-packages] [Bug 1400205] [NEW] network-manager may start before libsystemd-logind
Public bug reported: When NetworkManager starts, it requests systemd login-monitor notifications through the libsystemd-login sd_login_monitor_new(3) API. This API will fail if the systemd-logind service has not been started, since it directly accesses directories in /run/systemd. As far as I can tell, systemd-logind in Utopic is started on-demand (through DBUS service activation). So, there's no guarantee that it has been started at the point during boot when NetworkMonitor is started. I attached a patch to upstart .conf file with one way to fix it -- it contacts the DBUS logind API within pre-start to ensure it has been started. NOTE: you will not see the error in syslog -- NetworkManager logs it to stderr which is /dev/null. If you enable --no-daemon on NetworkManager, the error (sd_login_monitor_new failed) should get logged to /var/log/upstart/network-manager.log. NOTE: even with this fix, I saw that sd_login_monitor_new failed -- I believe that's a bug in Utopic's systemd (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203). I had to patch both to resolve a suspend/resume issue for me. Seen on: Ubuntu 14.10 NetworkManager 0.9.8.8-0ubuntu28 libsystemd-login0 208-8ubuntu8 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Patch added: network-manager-logind.patch https://bugs.launchpad.net/bugs/1400205/+attachment/4275943/+files/network-manager-logind.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1400205 Title: network-manager may start before libsystemd-logind Status in network-manager package in Ubuntu: New Bug description: When NetworkManager starts, it requests systemd login-monitor notifications through the libsystemd-login sd_login_monitor_new(3) API. This API will fail if the systemd-logind service has not been started, since it directly accesses directories in /run/systemd. As far as I can tell, systemd-logind in Utopic is started on-demand (through DBUS service activation). So, there's no guarantee that it has been started at the point during boot when NetworkMonitor is started. I attached a patch to upstart .conf file with one way to fix it -- it contacts the DBUS logind API within pre-start to ensure it has been started. NOTE: you will not see the error in syslog -- NetworkManager logs it to stderr which is /dev/null. If you enable --no-daemon on NetworkManager, the error (sd_login_monitor_new failed) should get logged to /var/log/upstart/network-manager.log. NOTE: even with this fix, I saw that sd_login_monitor_new failed -- I believe that's a bug in Utopic's systemd (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203). I had to patch both to resolve a suspend/resume issue for me. Seen on: Ubuntu 14.10 NetworkManager 0.9.8.8-0ubuntu28 libsystemd-login0 208-8ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205/+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
