Bug#757348: [systemd-shim] Re: systemd: with SysV init, can no? longer suspend and shutdown from lightdm

2014-10-13 Thread Marcin Szewczyk
d to unstable/testing. -- Marcin Szewczyk http://wodny.org mailto:marcin.szewc...@wodny.borg <- remove b / usuń b xmpp:wo...@ubuntu.pl xmpp:wo...@jabster.pl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "u

Bug#757348: [systemd-shim] Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

2014-10-12 Thread Marcin Szewczyk
On Sun, Oct 12, 2014 at 06:09:46PM +0200, Marcin Szewczyk wrote: > On Sun, Oct 12, 2014 at 05:25:43PM +0200, Marcin Szewczyk wrote: > > cgmanager: DEBUG per_ctrl_move_pid_main: 31385, memory - > > user.slice/user-1000.slice/session-c13.scope > > > > That means t

Bug#757348: [systemd-shim] Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

2014-10-12 Thread Marcin Szewczyk
On Sun, Oct 12, 2014 at 05:25:43PM +0200, Marcin Szewczyk wrote: > cgmanager: DEBUG per_ctrl_move_pid_main: 31385, memory - > user.slice/user-1000.slice/session-c13.scope > > That means that when systemd-shim calls cgmanager to MovePid/MovePidAbs > it uses a special controller nam

Bug#757348: [systemd-shim] Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

2014-10-12 Thread Marcin Szewczyk
it uses a special controller name "all". But it seems "all" doesn't include some controllers -- for example "name=systemd". Questions are: 1) Should cgmanager move pid to "name=systemd" when called with "all" controller? 2) Should systemd-sh

Bug#757348: [systemd-shim] Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

2014-10-10 Thread Marcin Szewczyk
gi-bin/bugreport.cgi?bug=728361#203 [2] https://wiki.ubuntu.com/DebuggingDBus [3] https://bugs.freedesktop.org/show_bug.cgi?id=80186 -- Marcin Szewczyk http://wodny.org mailto:marcin.szewc...@wodny.borg <- remove b / usuń b xmpp:wo...@ubuntu.pl xmpp:wo

Bug#740163: lxsession: lxlock/dm-tool lock is easily circumvented

2014-02-26 Thread Marcin Szewczyk
Package: lxsession Version: 0.4.9.2-1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, as described in bug #735854, locking doesn't work. It's a serious problem because after invoking lxlock the screen switches to VT8 with a login prompt and it looks like it locke