We discussed that again via email. In summary:
- UAL and systemd units are non-overlapping use cases, and will not collide
at all in practical use cases.
- By itself, systemd only handles the systemd controller, which cgmanager
should always stay out of
- systemd units may configure
We discussed that again via email. In summary:
- UAL and systemd units are non-overlapping use cases, and will not collide
at all in practical use cases.
- By itself, systemd only handles the systemd controller, which cgmanager
should always stay out of
- systemd units may configure
Discussed on IRC again. cgmanager changes the systemd controller and
thus interferes with systemd. Also, in Ubuntu (not upstream or in
Debian), we have a systemd patch to put logind sessions into all cgroup
controllers (not just the systemd one) for supporting LXC user
containers, which would
If we can't start cgmanager automatically in Debian because it interacts
badly with systemd's cgroup management, this would just as well apply
to Ubuntu.
No, the reason we cannot enable it in debian is not because it'll
break systemd. It does run fine.
So *if* we can run them side by side,
Discussed on IRC again. cgmanager changes the systemd controller and
thus interferes with systemd. Also, in Ubuntu (not upstream or in
Debian), we have a systemd patch to put logind sessions into all cgroup
controllers (not just the systemd one) for supporting LXC user
containers, which would
I got u-desktop-next to boot, and confirm that starting cgmanager fixes
app startup.
** Package changed: systemd (Ubuntu) = cgmanager (Ubuntu)
** Changed in: cgmanager (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I put yesterday's desktop-next-amd64 image on an USB stick and booted
it on my thinkpad x230, but I don't get very far (bad video modes, I see
the welcome to your phone wizard, but aside from being able to move
the mouse cursor nothing works, it's just stuck there), so I can't test
this directly.
I got u-desktop-next to boot, and confirm that starting cgmanager fixes
app startup.
** Package changed: systemd (Ubuntu) = cgmanager (Ubuntu)
** Changed in: cgmanager (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Martin,
you marked this as affecting cgmanager. Could you be more specific
about what the bug in cgmanager is?
If it is just that you want cgmanager to start automatically under
systemd, then we will have to do that in ubuntu-specific packaging. We
cannot do that in the debian packaging.
Serge: Yes, that's what I meant. I'd prefer getting this fixed properly
in UAL, but if we need cgmanager for that, we can start it for that.
If we can't start cgmanager automatically in Debian because it interacts
badly with systemd's cgroup management, this would just as well apply
to Ubuntu.
unity8/qtmir relies on ubuntu-app-launch for all application management,
so fix is for UAL to get systemd support
** Also affects: ubuntu-app-launch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
having ubuntu-launch-app using systemd is orthogonal to this issue, in
the current config upstart is still used for the user session and
working correctly, only the system init changed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
12 matches
Mail list logo
