[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-10-25 Thread Marcos Alano
A error reported by Cristian is driving me crazy: [ 16.972759] systemd-logind[1097]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 16.972770] systemd-logind[1097]: Failed to start user service: Unknown unit: user@1000.service Any ideas? I use Utopic. -- You

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-29 Thread Martin Pitt
I believe this has been sufficiently tested now. We are out of traincon-0 for the touch images too, so let's unleash this. ** Changed in: systemd (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-25 Thread Martin Pitt
** Changed in: systemd (Ubuntu) Status: In Progress = Fix Committed -- 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/1346199 Title: Needs testing in -proposed:

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-24 Thread Cavsfan
I enabled Pre-Release updates and got just the following: libpam-systemd (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2 libsystemd-daemon0 (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2 libsystemd-journal0 (version 204-14ubuntu2) will be upgraded to version

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Martin Pitt
I tested this in a system-level container with -proposed enabled, i. e. systemd/logind 208 with shim and cgmanager on both the host and the container. loginctl, udev, proc/self/cgroup etc. all look fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Martin Pitt
I installed the proposed version on current Phone image 141, and tested reboot, dialer, bluetooth pairing with a headset, battery indicator reaction to plug/unplug, autopilot tests for calculator app, /dev automatic ACLs, loginctl, and udevadm. All work fine. -- You received this bug

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Cristian Aravena Romero
Now reboo Se actualizarán los siguientes paquetes: libpam-systemd libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 systemd 5 paquetes actualizados, 0 nuevos instalados, 0 para eliminar y 182 sin actualizar. Necesito

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Cristian Aravena Romero
Update others packages $ sudo aptitude install libsystemd-login0 libsystemd-login0:i386 libsystemd-login-dev libsystemd-login-dev:i386 Se instalarán los siguiente paquetes NUEVOS: libsystemd-login-dev libsystemd-login-dev:i386

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Harry
The new systemd (208-6ubuntu1) works fine on my setup: fully updated Utopic (amd64) with nvidia proprietary drivers. I tested this with systemd booting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Martin Pitt
Anders: When you boot with upstart, can you please attach /var/log/auth.log after booting? I'm not sure why restarting gdm would work, but maybe there's a libpam_systemd error message in there? If you try and log into VT1 right after boot, does that work? I. e. do you see a session for that in

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Martin Pitt
** Description changed: I just uploaded systemd 208-6ubuntu1 to utopic-proposed, which makes use of the new cgmanager-enabled systemd-shim. This bug prevents this new version to migrate to utopic until we get more confirmation that this doesn't regress udev/logind. I already tested