[Bug 1580984] Re: procps postinst fails when inside lxd
procps has a patch to sysctl.c to ignore EACCESS. I guess systemd's systemd-sysctl needs the same kind of patch. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: lxd (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1580984 Title: procps postinst fails when inside lxd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1580984/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574566] Re: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks, but actually the systemd.service(5) manpage tells me what I needed. The fix for you should be to edit your /lib/systemd/system/libvirt- bin.service file to read: [Unit] Description=Virtualization daemon Before=libvirt-guests.service After=network.target After=dbus.service After=iscsid.service After=apparmor.service After=local-fs.target After=remote-fs.target Documentation=man:libvirtd(8) Documentation=http://libvirt.org [Service] Type=notify EnvironmentFile=-/etc/default/libvirt-bin ExecStart=/usr/sbin/libvirtd $libvirtd_opts ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure LimitNOFILE=infinity LimitNPROC=infinity TasksMax=infinity NotifyAccess=all [Install] WantedBy=multi-user.target Also=virtlockd.socket Also=virtlogd.socket In other words, just add the NotifyAccess=all line in the second section. I'll push that to the 16.10 package and SRU the change to wily and xenial. Thanks! ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574566 Title: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574566] Re: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Do we need to add NotifyAccess=all to the systemd job? ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Red Hat Bugzilla #1047304 https://bugzilla.redhat.com/show_bug.cgi?id=1047304 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574566 Title: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1569064] [NEW] systemctl wants to configure interfaces it shouldn't (lxdbr0)
Public bug reported: The reproducer: create a xenial vm. There, run lxc launch ubuntu: leave that container running, and reboot. If you're "lucky", networking will never come up: [[0;32m OK [0m] Found device /sys/subsystem/net/devices/lxdbr0. [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s / 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m] A start job is running for Raise network interfaces (33s / 5min 11s)[K[[0;31m*[0;1;31m*[0m[0;31m* [0m] A start job i s running for Raise network interfaces (34s / 5min 11s)[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for Raise network interfaces (34s / 5min 11s)[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for Raise network interfaces (35s / 5min 11s)[K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job is running for Raise network interfaces (35 s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise network interfaces (36s / 5min 11s)[K[ [0 ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job i (etc) I can reproduce this 100% on serverstack (openstack) instances. I cannot reproduce it locally with uvt-kvm. What appears to be happening is that lxd starts lxd-bridge which creates lxdbr0 with no ipv4 address; this racily happens before systemd does its networking setup; said network setup then sees lxdbr0 and wants to configure it, so waits for it to have an ip address. Plausible? ** Affects: lxd (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: systemctl wants to configure interfaces it shouldn't (lxdbr0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1569064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug
** Changed in: cgmanager (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1392176 Title: mounts cgroups unconditionally which causes undesired effects with cpu hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1533833] Re: unprivileged lxc containers won't start
systemd should be updated to know about the pids cgroup ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: lxc (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Wily) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1533833 Title: unprivileged lxc containers won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1533833] Re: unprivileged lxc containers won't start
You're using a newer kernel which provides the 'pids' cgroup. Systemd doesn't know about that one and so doesn't create a cgroup for you that you own. Lxc in turn (in wily) doesn't yet know how to handle that. You can work around this several ways. The simplest is to do sudo cgm create pids user sudo cgm chown pids user $(id -u) $(id -g) cgm movepid pids user $$ before you start the container. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Importance: Undecided => Medium ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1533833 Title: unprivileged lxc containers won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1497420] Re: systemd 226-2 (debian sid) breaks lxc-attach
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #798778 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798778 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798778 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1497420 Title: systemd 226-2 (debian sid) breaks lxc-attach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1497420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1491557] Re: Nested containers aren't working in wily
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1491557 Title: Nested containers aren't working in wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1491557/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1491557] Re: Nested containers aren't working in wily
D'oh, sorry, i didn't see your comments in time and pushed to ubuntu pkg myself. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1491557 Title: Nested containers aren't working in wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1491557/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1491557] [NEW] Nested containers aren't working in wily
Public bug reported: Several things are conspiring to stop nested containers in wily from working. ** Affects: cgmanager (Ubuntu) Importance: High Assignee: Serge Hallyn (serge-hallyn) Status: In Progress ** Affects: lxcfs (Ubuntu) Importance: High Assignee: Serge Hallyn (serge-hallyn) Status: In Progress ** Affects: systemd (Ubuntu) Importance: High Assignee: Serge Hallyn (serge-hallyn) Status: In Progress ** Also affects: lxcfs (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: cgmanager (Ubuntu) Importance: Undecided => High ** Changed in: lxcfs (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: cgmanager (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) ** Changed in: lxcfs (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) ** Changed in: cgmanager (Ubuntu) Status: New => In Progress ** Changed in: lxcfs (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1491557 Title: Nested containers aren't working in wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1491557/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1467611] Re: unprivileged lxc containers broken
The cgmanager log shows: Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh- server.service/lxc/asterisk How are you logged in when you try to start the container? To start an unprivileged container, you must be logged into a regular user session, so /proc/self/cgroup should look something like: 10:memory:/user.slice/user-1000.slice/session-c2.scope 9:perf_event:/user.slice/user-1000.slice/session-c2.scope 8:cpu,cpuacct:/user.slice/user-1000.slice/session-c2.scope 7:cpuset:/user.slice/user-1000.slice/session-c2.scope 6:net_cls,net_prio:/user.slice/user-1000.slice/session-c2.scope 5:blkio:/user.slice/user-1000.slice/session-c2.scope 4:hugetlb:/user.slice/user-1000.slice/session-c2.scope 3:devices:/user.slice/user-1000.slice/session-c2.scope 2:freezer:/user.slice/user-1000.slice/session-c2.scope 1:name=systemd:/user.slice/user-1000.slice/session-c2.scope Instead you seem to be in /system.slice/lsh-server.service, which you do not own. So as an unprivileged user you cannot create new cgroups for yourself, which is why lxc is failing. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1467611 Title: unprivileged lxc containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1467611/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1413927] Re: lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid requestUser container fails to start:
** Package changed: lxc (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Summary changed: - lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid requestUser container fails to start: + login name=systemd cgroup is not owned by user ** Description changed: + When a user logs in, systemd-logind should create cgroups for the user, + with the directory (i.e. /user.slice/user-1000.slice/session-c2.scope) + and the tasks and cgroup.procs files (but no othes) owned by the user. + This is no longer hapening for the name=systemd cgroup. This prevents + containers from starting. (If lxc were to simply not create/use that + controller, then it would prevent system in the container from using + it). + I wanted to test the new lxc with lxcfs. A system container (with upstart or systemd) works perfectly well now (great!), but user containers regressed: $ lxc-create -n v1 -t download -- -d ubuntu -r vivid -a amd64 - $ lxc-start -n v1 -F + $ lxc-start -n v1 -F lxc-start: cgmanager.c: lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid request lxc-start: start.c: __lxc_start: 1099 failed to spawn 'v1' lxc-start: lxc_start.c: main: 345 The container failed to start. My host is running systemd, but cgmanager is running (i. e. it's not bug 1400394, I enabled cgmanager.service). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 23 10:35:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-20 (63 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up - lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.lxcpath = /srv/lxc -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1413927 Title: login name=systemd cgroup is not owned by user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413927/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1355966] Re: [FFE] Implement AbandonScope (etc)
** Changed in: cgmanager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1355966 Title: [FFE] Implement AbandonScope (etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1355966/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1355966] Re: [FFE] Implement AbandonScope (etc)
** Also affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Changed in: cgmanager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1355966 Title: [FFE] Implement AbandonScope (etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1355966/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1355966] [NEW] Implement AbandonScope (etc)
Public bug reported: Currently, logout produces the following error in upstart systems: systemd-logind[15351]: Failed to abandon scope session-c7.scope systemd-logind[15351]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc7_2escope Whlie the cgroup is being autoremoved when empty, the more important bug is that StopSession won't forcibly kill the cgroup. These methods should be added at some point. ** Affects: systemd-shim (Ubuntu) Importance: Medium Assignee: Serge Hallyn (serge-hallyn) Status: Confirmed ** Changed in: systemd-shim (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd-shim (Ubuntu) Status: New => Confirmed ** Changed in: systemd-shim (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1355966 Title: Implement AbandonScope (etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1355966/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1309025] Re: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL
** Changed in: cgmanager (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1309025 Title: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1309025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1317179] Re: lxc containers fail to start in trusty with newer kernels
Now that's odd. This certainly seemed to be fixed in utopic, but after a quick dist-upgrade from a trusty host net_cls in fact does not appear to be there. So I think you're right - thanks! status: confirmed ** Changed in: systemd (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1317179 Title: lxc containers fail to start in trusty with newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1317179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317179] Re: lxc containers fail to start in trusty with newer kernels
The variable JoinControllers in /etc/systemd/system.cofn should include net_cls. Otherwise when newer kernel is used in trusty, users will not by default be able to use unprivileged containers. ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1317179 Title: lxc containers fail to start in trusty with newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1317179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317179] Re: lxc containers fail to start in trusty with newer kernels
** No longer affects: lxc -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1317179 Title: lxc containers fail to start in trusty with newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1317179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1309025] Re: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL
Thanks, everyone. I don't believe anything in cgmanager fixed this, so rather than mark it 'fix released' i'll mark it 'invalid' in the 'can no longer be reproduced' sense. If it happens again please do reopen this. status: invalid ** Changed in: cgmanager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1309025 Title: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1309025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
** Changed in: libnih (Ubuntu) Status: Confirmed => Invalid ** Changed in: cgmanager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
It turns out the write() is not a part of the dbus transaction with
cgmanager, but actually a part of libnih's mainloop exiting code:
(gdb) where
#0 0x7f70ea509700 in __write_nocancel () at
../sysdeps/unix/syscall-template.S:81
#1 0x7f70eae47377 in nih_main_loop_interrupt () at main.c:630
#2 0x7f70eaa0d64b in _dbus_transport_queue_messages
(transport=transport@entry=0x2329290) at ../../dbus/dbus-transport.c:1157
#3 0x7f70eaa0df8e in do_reading (transport=0x2329290) at
../../dbus/dbus-transport-socket.c:851
#4 0x7f70eaa0e626 in socket_do_iteration (transport=0x2329290, flags=6,
timeout_milliseconds=) at ../../dbus/dbus-transport-socket.c:1162
#5 0x7f70eaa0d3ff in _dbus_transport_do_iteration (transport=0x2329290,
flags=3940863025, flags@entry=6, timeout_milliseconds=1,
timeout_milliseconds@entry=25000) at ../../dbus/dbus-transport.c:976
#6 0x7f70ea9f79dc in _dbus_connection_do_iteration_unlocked
(connection=connection@entry=0x232d580, pending=pending@entry=0x232bf90,
flags=flags@entry=6,
timeout_milliseconds=timeout_milliseconds@entry=25000) at
../../dbus/dbus-connection.c:1234
#7 0x7f70ea9f8389 in _dbus_connection_block_pending_call
(pending=0x232bf90) at ../../dbus/dbus-connection.c:2415
#8 0x7f70eaa0772a in dbus_pending_call_block (pending=) at
../../dbus/dbus-pending-call.c:748
#9 0x7f70ea9f894d in dbus_connection_send_with_reply_and_block
(connection=0x232d580, message=0x23056e0, timeout_milliseconds=-1,
error=0x7fff22097b70)
at ../../dbus/dbus-connection.c:3530
#10 0x7f70eb05b4f5 in cgmanager_create_sync () from
/lib/x86_64-linux-gnu/libcgmanager.so.0
#11 0x00422520 in ?? ()
#12 0x004164a4 in ?? ()
#13 0x0041655d in ?? ()
#14 0x0040f3ed in ?? ()
#15 0x004107dc in ?? ()
#16 0x0040c4d3 in ?? ()
#17 0x7f70eaa06e26 in _dbus_object_tree_dispatch_and_unlock
(tree=0x22f92a0, message=message@entry=0x22fb9d0,
found_object=found_object@entry=0x7fff22098114)
at ../../dbus/dbus-object-tree.c:862
#18 0x7f70ea9f9a01 in dbus_connection_dispatch (connection=0x22f8870) at
../../dbus/dbus-connection.c:4672
#19 0x00409467 in ?? ()
#20 0x0040622c in ?? ()
#21 0x7f70ea43eec5 in __libc_start_main (main=0x4060d0, argc=1,
argv=0x7fff220982d8, init=, fini=,
rtld_fini=,
stack_end=0x7fff220982c8) at libc-start.c:287
#22 0x0040637c in ?? ()
This is happening in this part of nih/main.c:
/**
* nih_main_loop_interrupt:
*
* Interrupts the current (or next) main loop iteration because of an
* event that potentially needs immediate processing, or because some
* condition of the main loop has been changed.
**/
void
nih_main_loop_interrupt (void)
{
nih_main_loop_init ();
if (interrupt_pipe[1] != -1)
while (write (interrupt_pipe[1], "", 1) < 0)
;
}
Why the interrupt_pipe[0] woudl be closed is beyond me.
A simple fix would be to add a check for errno == EAGAIN in the while
loop to avoid this condition. However, we should figure out why this is
happening and hopefully we can prevent it happening at all.
** Also affects: libnih (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libnih (Ubuntu)
Importance: Undecided => High
** Changed in: libnih (Ubuntu)
Status: New => Confirmed
** Changed in: cgmanager (Ubuntu)
Importance: Undecided => High
** Changed in: cgmanager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1303649
Title:
systemd-logind spins in cgmanager_ping_sync()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 888662] Re: Web browsers should share the cache
** Changed in: w3m (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/888662 Title: Web browsers should share the cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amaya/+bug/888662/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 995817] Re: share samba doesn't work easily
Hi J-Paul, I'm pretty sure you are right and system-config-samba should not be needed. You were trying to share files through nautilus which should do it itself. If I'm wrong about that and it cannot, then it should be automatically installing it. In either case, I'll re-target this bug at nautilus. ** Package changed: samba (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/995817 Title: share samba doesn't work easily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/995817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 30554] Re: rhythmbox columns are not in "right" order
Thanks for the patch, Chris. Worked fine for me. I've filled in the patch headers, added a changelog entry, and proposed the result for merging (https://code.launchpad.net/~serge- hallyn/ubuntu/precise/rhythmbox/rhythmbox-sort/+merge/95646). Thanks again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/30554 Title: rhythmbox columns are not in "right" order To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/30554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 911305] Re: segfault from p11-kit when starting mutt with imap-over-ssl
Fixed for me too :) thanks for pointing that out. I'll re-target this bug and mark it closed. ** Changed in: p11-kit (Ubuntu) Status: Confirmed => Fix Released ** Package changed: p11-kit (Ubuntu) => gnome-keyring (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/911305 Title: segfault from p11-kit when starting mutt with imap-over-ssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/911305/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
