Debian Bug report logs - #757348
systemd: with SysV init, can no longer suspend and shutdown from lightdm

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Thu, 7 Aug 2014 13:03:38 +0200

Package: systemd
Version: 208-7
Severity: important

The systemd upgrade from 204-14 to 208-7 introduced a regression in
lightdm: the "Suspend", "Hibernate", "Restart" and "Shut Down" menu
items of lightdm are now greyed out (even before the first login).

Note: I'm using SysV init.

-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl                  2.2.52-1
ii  adduser              3.113+nmu3
ii  initscripts          2.88dsf-53.3
ii  libacl1              2.2.52-1
ii  libaudit1            1:2.3.7-1
ii  libblkid1            2.20.1-5.8
ii  libc6                2.19-7
ii  libcap2              1:2.24-4
ii  libcap2-bin          1:2.24-4
ii  libcryptsetup4       2:1.6.4-4
ii  libdbus-1-3          1.8.6-1
ii  libgcrypt11          1.5.3-5
ii  libkmod2             18-1
ii  liblzma5             5.1.1alpha+20120614-2
ii  libpam0g             1.1.8-3
ii  libselinux1          2.3-1
ii  libsystemd-daemon0   208-7
ii  libsystemd-journal0  208-7
ii  libsystemd-login0    208-7
ii  libudev1             208-7
ii  libwrap0             7.6.q-25
ii  sysv-rc              2.88dsf-53.3
ii  udev                 208-7
ii  util-linux           2.20.1-5.8

Versions of packages systemd recommends:
ii  libpam-systemd  208-7

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore


-- debconf-show failed

Message #10 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Vincent Lefevre <vincent@vinc17.net>, 757348@bugs.debian.org

Subject: Re: Bug#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Thu, 07 Aug 2014 13:11:38 +0200

[Message part 1 (text/plain, inline)]

reassign 757348 systemd-shim
thanks

Am 07.08.2014 13:03, schrieb Vincent Lefevre:
> Package: systemd
> Version: 208-7
> Severity: important
> 
> The systemd upgrade from 204-14 to 208-7 introduced a regression in
> lightdm: the "Suspend", "Hibernate", "Restart" and "Shut Down" menu
> items of lightdm are now greyed out (even before the first login).
> 
> Note: I'm using SysV init.
> 

Re-assigning to systemd-shim then, since that is used when sysvinit is used.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #15 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Michael Biebl <biebl@debian.org>

Cc: 757348@bugs.debian.org

Subject: Re: Bug#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Thu, 7 Aug 2014 16:31:52 +0200

Control: reassign -1 systemd-shim

On 2014-08-07 13:11:38 +0200, Michael Biebl wrote:
> reassign 757348 systemd-shim

It wasn't taken into account. Really reassigning...

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Message #26 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Clement Hermann <nodens@nodens.org>

To: 757348@bugs.debian.org

Subject: Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Thu, 07 Aug 2014 17:19:45 +0200

[Message part 1 (text/plain, inline)]

I suspect the same issue causes the following problems in gnome-shell :

- can't see the network connections (network-manager restart does make
them apear, but I cant act on them from GNOME)
- Can't suspend / restore / lock session


Also GDM fails to find the session ID and doesn't work at all :

gnome-session[6374]: WARNING: Could not get session id for session.
Check that l
ogind is properly installed and pam_systemd is getting used at login.

lightdm works but with the above gnome-shell issues.

Cheers,

-- 
Clément (nodens)

[Message part 2 (text/html, inline)]

Message #33 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Щербаков Дима <scherbakoff.dima@yandex.ru>

To: 757348@bugs.debian.org

Subject: Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Tue, 26 Aug 2014 14:36:39 +0600

Subject: Re: systemd: with SysV init, can no longer suspend and shutdown 
from lightdm
Followup-For: Bug #757348
Package: systemd-shim
Version: 7-1

Dear Maintainer,


I'm using KDE and no options like suspend and hibernate are now available in
power settings and KRunner.

   * What led up to the situation?
Switching back from systemd to simple working sysvinit.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I 've tried to google this problem, downgraded upower to previous 
version. Only
temporarily setting systemd as init in Grub boot options helped, these 
buttons
had shown in KRunner and I've set power setting.
After rebooting with sysvinit, they disappeared again, but display lid 
sleep-
on-close is working, at least.
So, now, I've minimal working sleep-on-close, but I've to manually use "sudo
s2ram/pm-suspend", instead of pressing according button in KRunner.
Could you fix it, please?
Thanks in advance :)



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (20, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd-shim depends on:
ii  cgmanager     0.30-1
ii  libc6         2.19-9
ii  libglib2.0-0  2.40.0-4

systemd-shim recommends no packages.

Versions of packages systemd-shim suggests:
ii  pm-utils  1.4.1-15

-- no debconf information

Message #36 received at 757348-submitter@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>

To: 747348-submitter@bugs.debian.org

Subject: Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Fri, 5 Sep 2014 16:34:58 -0700

Hi Vincent,

I've just uploaded systemd-shim 7-3, which includes a fix for a race
condition that could cause a user's processes to not be correctly associated
with the login session.  This would definitely explain the symptoms you're
seeing.  Could you please re-test with 7-3 and see if it fixes the problem
for you?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Message #43 received at 757348-quiet@bugs.debian.org (full text, mbox, reply):

From: victory <victory.deb@gmail.com>

To: Kitty Box <kittyofthebox@gmail.com>, 757348-quiet@bugs.debian.org

Subject: Re: Bug#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Mon, 8 Sep 2014 15:30:16 +0900

please do not continue to send to a submitter of wrong bug.
the message below was send to a wrong bug, which is not visible on #757348.
---
On Mon, 8 Sep 2014 16:18:00 +1000
Kitty Box wrote:

> Hi,
> 
> >Could you please re-test with 7-3 and see if it fixes the problem
> for you?
> 
> I decided to test this myself, systemd-shim version 7-3 did not fix
> the problem I think lightdm is effected by a similar issue effecting
> kde see this bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747180 as it might
> be related to this issue as well.
> 
> I also observed the same conditons as the original bug reporter when
> changing my init to systemd lightdm showed me the options on sysvinit
> they are all greyed out.
> 
> Kitty


-- 
victory

Message #50 received at 757348-quiet@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Steve Langasek <vorlon@debian.org>, 757348-quiet@bugs.debian.org

Subject: Re: Bug#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Tue, 9 Sep 2014 17:30:28 +0200

Control: found -1 7-3

On 2014-09-05 16:34:58 -0700, Steve Langasek wrote:
> I've just uploaded systemd-shim 7-3, which includes a fix for a race
> condition that could cause a user's processes to not be correctly
> associated with the login session. This would definitely explain the
> symptoms you're seeing. Could you please re-test with 7-3 and see if
> it fixes the problem for you?

Still the same problem after upgrading the systemd packages
from 204-14 to 208-8 (tested after a reboot).

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Message #59 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: 756076@bugs.debian.org, 757348@bugs.debian.org

Subject: Raise severity of bugs as requested.

Date: Thu, 18 Sep 2014 22:31:34 +0200

Control: severity 756076 grave
Control: severity 757348 grave

Steve Langasek wrote:
"If the systemd-shim package is currently broken and should not be allowed to
satisfy the libpam-systemd dependency, then that should be expressed as a
release-critical bug keeping it out of the release[...]"

Raising the severity of a couple of bugs that breaks the system in
various ways for users who for some reason ends up with systemd-shim
rather then the real deal as requested.

Regards,
Andreas Henriksson

Message #64 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>

To: 757348@bugs.debian.org

Cc: andreas@fatal.se

Subject: systemd-shim: Re: Raise severity of bugs as requested.

Date: Sun, 28 Sep 2014 10:12:11 -0700

[Message part 1 (text/plain, inline)]

On Thu, 18 Sep 2014 22:31:34 +0200 Andreas Henriksson 
<andreas@fatal.se> wrote:
>
> Control: severity 757348 grave

I would disagree that this particular bug (CanSuspend, CanShutdown, 
CanHibernate, etc. being reported as false) is of a grave severity. 
These are my reasons:

1) I can not reproduce it. This means that the package is not affecting 
every (or even a majority) of users, and is not completely useless.
2) There is absolutely no chance of data loss here.
3) There is no security issues here (unlike the other bug you raised 
the priority of).

The only item above that is questionable would be (1) I think. I am not 
perfect on what bug severities' qualifications are, so if the "makes 
the package in question unusable" bit is satisfied by it being unusable 
for only one or a few users, then I retract my disagreement.

Otherwise, if you agree Andreas, please lower this back down to 
important.

Thank you,
--
Cameron Norman

[Message part 2 (text/html, inline)]

Message #69 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Cameron Norman <camerontnorman@gmail.com>, 757348@bugs.debian.org

Cc: andreas@fatal.se

Subject: Re: Bug#757348: systemd-shim: Re: Raise severity of bugs as requested.

Date: Sun, 28 Sep 2014 19:51:48 +0200

On 2014-09-28 10:12:11 -0700, Cameron Norman wrote:
> I would disagree that this particular bug (CanSuspend, CanShutdown,
> CanHibernate, etc. being reported as false) is of a grave severity. These
> are my reasons:
> 
> 1) I can not reproduce it. This means that the package is not affecting
> every (or even a majority) of users, and is not completely useless.

The last time I tried (not with the latest systemd-shim version),
it affected me too (I still use an old version of systemd because
of that).

Any reason why this only affects some users?

> 2) There is absolutely no chance of data loss here.

If because of this bug, one switches off the machine by pressing
the power button, there is a risk of data loss.

IMHO, having a machine that cannot be shutdown is a major problem.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Message #74 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: Cameron Norman <camerontnorman@gmail.com>

Cc: 757348@bugs.debian.org

Subject: Re: systemd-shim: Re: Raise severity of bugs as requested.

Date: Sun, 28 Sep 2014 20:17:09 +0200

On Sun, Sep 28, 2014 at 10:12:11AM -0700, Cameron Norman wrote:
> I would disagree that this particular bug (CanSuspend, CanShutdown,
> CanHibernate, etc. being reported as false) is of a grave severity. These
> are my reasons:
> 
> 1) I can not reproduce it. This means that the package is not affecting
> every (or even a majority) of users, and is not completely useless.

The problem is trivial to reproduce, so please try harder.
Just do a standard Jessie xfce install, install sysvinit-core and
systemd-shim to let it replace systemd-sysv. Try to suspend.
Multiple people has already reported running into this and people are
not able to figure out how to work around them. (And some of these users
are other Debian Developers I might add, so should supposedly be on the
more qualified side of the scale.)

Last time I tried xfce was the default desktop. Now that we moved
back to GNOME again, the problems are worse. People are reporting
not being able to even login because of systemd-shim failure.
(I can't help but wonder if anyone is actually testing systemd-shim at
all? If so, for which usecase are you testing or are you living in
some completely theoretical scenario? A default install would be a
useful addition to the testcases if it's not already there.)

> 2) There is absolutely no chance of data loss here.

If there where I'd use the critical severity.

> 3) There is no security issues here (unlike the other bug you raised the
> priority of).

If there where, I'd use the security tag.

> 
> The only item above that is questionable would be (1) I think. I am not
> perfect on what bug severities' qualifications are, so if the "makes the
> package in question unusable" bit is satisfied by it being unusable for only
> one or a few users, then I retract my disagreement.

I agree with this part, but it's probably more correct to guess that
you haven't actually read the policy and are just cargo-culting reasons
you've seen other people use without understanding them.

Please read debian policy if you really want to go on and argue about
severities. (But it would be so much more helpful if people would focus
on solving issues which makes users not be able to use their computers
properly instead of arguing about severities. I only raised the severities
because the maintainer wanted to get current issues pointed out better
as quoted in my previous mail.)

> 
> Otherwise, if you agree Andreas, please lower this back down to important.

No I don't agree. I'm also at the receiving end of people being frustrated
about all the random breakage systemd-shim creates. If people really want
to see systemd-shim be an alternative a whole bunch of bugs in it needs
to be fixed.

Help with doing user support is very much welcome because currently
the mere existance of systemd-shim raises whe workload alot here.

If people argue that systemd-shim is fine in its current state you
really need to bring and armada of people doing user support because
users reporting in don't agree with you.
If this armada of volunteers for user support doesn't exist, then
either systemd-shim needs to be fixed or made sure it's not tricking
users into using it (ie. removed from jessie).
This might sound harsh, but there are a bunch of more issues which
noone has bothered reassigning to systemd-shim yet as apparently
noone is taking care of the issues anyway. There really is a need
for a big effort to bring systemd-shim into a much better state
if it's going to fill the shoes it tries to claim.
These issues don't go away simply by arguing about bug severities.
Feel free to argue them with the maintainer of the package and keep
me out of the loop here so I can use my time to actually improve
Debian.


Regards,
Andreas Henriksson

Message #79 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>

To: 757348@bugs.debian.org

Subject: systemd-shim: logind sessions not being registered with lightdm

Date: Sun, 28 Sep 2014 12:31:41 -0700

[Message part 1 (text/plain, inline)]

Hello guys,

There is some info that may be helpful:

1) If you login on a console, is that session registered (use the bare 
`loginctl` command to list all registered sessions, or the last few 
lines of `dmesg`)?
2) What display managers are you using? Have you tried with any others 
and gotten different results?
3) Is your DE session also not registered with logind (again, use 
logind/dmesg to see)?
4) Can you paste the output of `grep pam_systemd /var/log/auth.log`?
5) Are there any error messages from logind in dmesg?

Of course, versions of libpam-systemd, systemd, and systemd-shim are 
useful.

For reference, the only errors that logind reports to me are that the 
user@ service was not started successfully, and the only issues I have 
are with the sessions not being cleared up when I log out. I have used 
gdm3, lightdm, and gnome to suspend/shutdown successfully. My 
systemd-shim version is 8-2, and systemd/libpam-systemd is 215-4.

Thank you,
--
Cameron

[Message part 2 (text/html, inline)]

Message #90 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: Debian Bug Tracking System <757348@bugs.debian.org>

Subject: Re: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Thu, 09 Oct 2014 15:22:15 +0530

Package: systemd-shim
Version: 8-2
Followup-For: Bug #757348

Hi, I'm hit by this bug and am not sure what the tag "fixed-upstream"
here is referring to ?

This issue is very well present and does not seem to have a fix yet.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd-shim depends on:
ii  cgmanager     0.32-4
ii  libc6         2.19-11
ii  libglib2.0-0  2.42.0-2

systemd-shim recommends no packages.

Versions of packages systemd-shim suggests:
pn  pm-utils  <none>

-- no debconf information

Message #95 received at 757348@bugs.debian.org (full text, mbox, reply):

From: OmegaPhil <OmegaPhil@startmail.com>

To: 757348@bugs.debian.org

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

Date: Thu, 09 Oct 2014 21:16:07 +0100

[Message part 1 (text/plain, inline)]

Package: systemd-shim
Version: 8-2

Fixed-upstream is invalid as this bug has recently had a number of
others merged into it.

I have spent a few days looking into this problem, and have had to start
from scratch to see what is going on.

I have been seeing what happens when you run 'pkcheck --list-temp',
which currently returns 'Error getting session: No session for pid <PID>'.

It looks like polkit has a hard dependency on systemd as init currently
- the 'session' being sought goes through
src/polkit/polkit/polkitunixsession-systemd.c:polkit_unix_session_initable_init,
which then calls into sd_pid_get_session from the libsystemd0 package.
This uses the PID of the pkcheck-calling process to read the proc file
'/proc/<pid>/cgroup' - it looks for a line containing 'systemd', and
then extracts the 'path', the bit at the end, to get at the session.

On my current session, every single process has '/' as this path - in
libsystemd0/systemd-215/src/shared/cgroup-util.c:cg_path_get_session
line 1320, this path is explicitly rejected - its checked for and
'-ENOENT' is returned.

Under a systemd-as-init system, a valid example of a path would be
'/user.slice/user-1000.slice/session-1.scope'.

So far I haven't seen logind factor in here. I can see that polkit used
to use ConsoleKit (I was originally expecting to be investigating
src/polkit/polkitunixsession.c rather than the systemd version), I hope
next session to turn back time a bit and see how this process worked
properly under ConsoleKit.

I know nothing about cgmanager yet BTW, I've been told it might be a bug
with this - will check into that later.

-- 
Libre software on Github: https://github.com/OmegaPhil
FSF member #9442

[signature.asc (application/pgp-signature, attachment)]

Message #100 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>

To: OmegaPhil <OmegaPhil@startmail.com>

Cc: 757348@bugs.debian.org

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

Date: Fri, 10 Oct 2014 16:19:51 +0200

[Message part 1 (text/plain, inline)]

I have done almost exactly the same research yesterday evening.

On Thu, Oct 09, 2014 at 09:16:07PM +0100, OmegaPhil wrote:
> It looks like polkit has a hard dependency on systemd as init currently
> - the 'session' being sought goes through
> src/polkit/polkit/polkitunixsession-systemd.c:polkit_unix_session_initable_init,
> which then calls into sd_pid_get_session from the libsystemd0 package.
> This uses the PID of the pkcheck-calling process to read the proc file
> '/proc/<pid>/cgroup' - it looks for a line containing 'systemd', and
> then extracts the 'path', the bit at the end, to get at the session.

It bothers me a bit. As I see this logind has its internal list of
sessions in its memory. On the other hand there is a hierarchy in
/sys/fs/cgroup/systemd which (using some specially formatted names)
codes session names. What happens if they desynchronize (for example
when the logind daemon dies)?

> On my current session, every single process has '/' as this path - in
> libsystemd0/systemd-215/src/shared/cgroup-util.c:cg_path_get_session
> line 1320, this path is explicitly rejected - its checked for and
> '-ENOENT' is returned.

Same here.

> Under a systemd-as-init system, a valid example of a path would be
> '/user.slice/user-1000.slice/session-1.scope'.

I have done an experiment:
/sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-1.scope
echo SHELLPID > /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-1.scope/tasks

Calls to polkit from that shell started working again.

After adding all the gvfs processes to that cgroup (using pgrep and echo
to tasks) I was able to mount a USB drive.

> So far I haven't seen logind factor in here.

The question is: who is responsible for adding my X11 process during its
startup to that specially named cgroup?

There are so many actors. pid eins, cgmanager, logind, lightdm, X11
scripts in /etc/X11, polkit, consolekit and PAM session modules (for
both consolekit and systemd).

One thing that seriously bothers me is that Jos van Wolput has
reported[1] that things started to work again after upgrading polkit
from 0.105-4 to 0.112-2. I really do not want to mess around with
experimental packages, so I have not checked it. But does it use
ConsoleKit again? Or does polkit has anything to do with assigning a
process to that specially named cgroup?

> I can see that polkit used to use ConsoleKit (I was originally
> expecting to be investigating src/polkit/polkitunixsession.c rather
> than the systemd version), I hope next session to turn back time a bit
> and see how this process worked properly under ConsoleKit.

That was a surprise for me as well. I have enabled eavesdropping[2][3]
for the system bus. I have launched dbus-monitors for both system and
session buses but nothing important has been sent through DBus.

ltrace was very helpful in finding out how is the session for a PID
found (partial ltrace output attached).

I also attach two simple programs that can be used to test if we are
able to find the session for a PID. One calls systemd directly, the
second one calls polkit (which currently calls the same systemd
function).


[1] https://bugs.debian.org/cgi-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.Szewczyk@wodny.borg  <- remove b / usuń b
xmpp:wodny@ubuntu.pl                  xmpp:wodny@jabster.pl

[Makefile (text/plain, attachment)]

[polkit-call.c (text/x-csrc, attachment)]

[polkit-part.ltrace (text/plain, attachment)]

[direct-systemd-call.c (text/x-csrc, attachment)]

Message #105 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>

To: 757348@bugs.debian.org

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

Date: Sat, 11 Oct 2014 16:54:14 -0700

[Message part 1 (text/plain, inline)]

On Fri, 10 Oct 2014 16:19:51 +0200 Marcin Szewczyk 
<Marcin.Szewczyk@wodny.org> wrote:
> I have done almost exactly the same research yesterday evening.
>
> On Thu, Oct 09, 2014 at 09:16:07PM +0100, OmegaPhil wrote:
> > It looks like polkit has a hard dependency on systemd as init 
currently
> > - the 'session' being sought goes through
> > 
src/polkit/polkit/polkitunixsession-systemd.c:polkit_unix_session_initable_init,
> > which then calls into sd_pid_get_session from the libsystemd0 
package.
> > This uses the PID of the pkcheck-calling process to read the proc 
file
> > '/proc/<pid>/cgroup' - it looks for a line containing 'systemd', 
and
> > then extracts the 'path', the bit at the end, to get at the 
session.
>
> It bothers me a bit. As I see this logind has its internal list of
> sessions in its memory. On the other hand there is a hierarchy in
> /sys/fs/cgroup/systemd which (using some specially formatted names)
> codes session names. What happens if they desynchronize (for example
> when the logind daemon dies)?

There is also /run/systemd/{seats,users,sessions}. I suspect these 
directories are to allow internal state to be recovered in case of a 
crash, you know? Not sure though.

>
> > On my current session, every single process has '/' as this path - 
in
> > 
libsystemd0/systemd-215/src/shared/cgroup-util.c:cg_path_get_session
> > line 1320, this path is explicitly rejected - its checked for and
> > '-ENOENT' is returned.
>
> Same here.

Are you sure you have cgmanager running? Maybe the sysvinit script has 
some problems; I am using Upstart al momento so maybe that is it.

>
> > Under a systemd-as-init system, a valid example of a path would be
> > '/user.slice/user-1000.slice/session-1.scope'.
>
> I have done an experiment:
> /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-1.scope
> echo SHELLPID > 
/sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-1.scope/tasks
>
> Calls to polkit from that shell started working again.
>
> After adding all the gvfs processes to that cgroup (using pgrep and 
echo
> to tasks) I was able to mount a USB drive.
>
> > So far I haven't seen logind factor in here.
>
> The question is: who is responsible for adding my X11 process during 
its
> startup to that specially named cgroup?
>
> There are so many actors. pid eins, cgmanager, logind, lightdm, X11
> scripts in /etc/X11, polkit, consolekit and PAM session modules (for
> both consolekit and systemd).

On sysvinit and Upstart, PID1 has nothing to do with this situation. On 
systemd, systemd puts the session init process into a cgroup. 
systemd-shim offers systemd's D-Bus interface and implements the 
cgroups bits (which logind is concerned with) through cgmanager. Can 
you tell me what your cgmanager version is?

Basically the flow is:

PAM module for logind calls the logind CreateSession() method
logind calls the systemd cgroup slice creation methods (delivered to 
systemd-shim)
systemd-shim calls the cgmanager cgroup methods, and the session init 
process is then put into the appropiate cgroup

I have this stuff working, and my /proc/$$/cgroup looks like so:

11:name=systemd:/user.slice/user-1000.slice/session-1.scope
10:perf_event:/user.slice/user-1000.slice/session-1.scope
9:net_prio:/user.slice/user-1000.slice/session-1.scope
8:net_cls:/user.slice/user-1000.slice/session-1.scope
7:memory:/user.slice/user-1000.slice/session-1.scope
6:freezer:/user.slice/user-1000.slice/session-1.scope
5:devices:/user.slice/user-1000.slice/session-1.scope
4:cpuset:/user.slice/user-1000.slice/session-1.scope
3:cpuacct:/user.slice/user-1000.slice/session-1.scope
2:cpu:/user.slice/user-1000.slice/session-1.scope
1:blkio:/user.slice/user-1000.slice/session-1.scope

> [snip]

Can you tell me what your systemd-shim and cgmanager versions are?

Thanks a ton,
--
Cameron Norman

[Message part 2 (text/html, inline)]

Message #110 received at 757348@bugs.debian.org (full text, mbox, reply):

From: OmegaPhil <OmegaPhil@startmail.com>

To: 757348@bugs.debian.org

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

Date: Sun, 12 Oct 2014 14:01:06 +0100

[Message part 1 (text/plain, inline)]

Thanks Marcin for taking the investigation further - running in the
normal sysv-as-init system, I don't have the 'user.slice' directory
under '/sys/fs/cgroup/systemd' - just a collection of empty files:

===============================

$ /sys/fs/cgroup/systemd$ file *

cgroup.clone_children: empty
cgroup.procs:          empty
cgroup.sane_behavior:  empty
notify_on_release:     empty
release_agent:         empty
tasks:                 empty

===============================

I have tested polkit from experimental (sudo aptitude install -t
experimental policykit-1 libpolkit-agent-1-0 libpolkit-gobject-1-0
libsystemd-login0 libpam-systemd) and I still get the same issue.

Thanks for the ltrace note - I've been using gdb with '-ggdb3 -Og'
recompiled packages.


On 12/10/14 00:54, Cameron Norman wrote:

> Are you sure you have cgmanager running? Maybe the sysvinit script has
> some problems; I am using Upstart al momento so maybe that is it.

cgmanager is running both in my test VM and on this machine.


> Can you tell me what your systemd-shim and cgmanager versions are?

cgmanager: 0.32-4
systemd-shim: 8-2

I'll see if I can understand what is breaking from what you have said.

-- 
Libre software on Github: https://github.com/OmegaPhil
FSF member #9442

[signature.asc (application/pgp-signature, attachment)]

Message #115 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>

To: OmegaPhil <OmegaPhil@startmail.com>

Cc: 757348@bugs.debian.org

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

Date: Sun, 12 Oct 2014 17:25:43 +0200

On Sun, Oct 12, 2014 at 02:01:06PM +0100, OmegaPhil wrote:
> On 12/10/14 00:54, Cameron Norman wrote:
> > Can you tell me what your systemd-shim and cgmanager versions are?
> 
> cgmanager: 0.32-4
> systemd-shim: 8-2

Same versions here.

I have added some debug to cgmanager and this is what I saw:
cgmanager: DEBUG move_pid_main: all - user.slice/user-1000.slice/session-c13.scope
cgmanager: DEBUG per_ctrl_move_pid_main: 31385, blkio - user.slice/user-1000.slice/session-c13.scope
cgmanager: DEBUG per_ctrl_move_pid_main: 31385, cpu - user.slice/user-1000.slice/session-c13.scope
cgmanager: DEBUG per_ctrl_move_pid_main: 31385, cpuacct - user.slice/user-1000.slice/session-c13.scope
cgmanager: DEBUG per_ctrl_move_pid_main: 31385, cpuset - user.slice/user-1000.slice/session-c13.scope
cgmanager: DEBUG per_ctrl_move_pid_main: 31385, devices - user.slice/user-1000.slice/session-c13.scope
cgmanager: DEBUG per_ctrl_move_pid_main: 31385, freezer - user.slice/user-1000.slice/session-c13.scope
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 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-shim call cgmanager with "all" and then with
   "name=systemd"?

-- 
Marcin Szewczyk                       http://wodny.org
mailto:Marcin.Szewczyk@wodny.borg  <- remove b / usuń b
xmpp:wodny@ubuntu.pl                  xmpp:wodny@jabster.pl

Message #120 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>

To: OmegaPhil <OmegaPhil@startmail.com>

Cc: 757348@bugs.debian.org, Cameron Norman <camerontnorman@gmail.com>

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

Date: Sun, 12 Oct 2014 18:09:46 +0200

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 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?

So, I think it should and it would. I omitted very important line from
my previous log:

cgmanager: DEBUG per_ctrl_move_pid_main: 31385, memory - user.slice/user-1000.slice/session-c13.scope
cgmanager: Found no cgroup entry for pid 31388 controller memory

The thing is -- cgmanager jumps out from the "all" loop after some
problem with the "memory" controller. I do not know what to do with it
yet.

-- 
Marcin Szewczyk                       http://wodny.org
mailto:Marcin.Szewczyk@wodny.borg  <- remove b / usuń b
xmpp:wodny@ubuntu.pl                  xmpp:wodny@jabster.pl

Message #125 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>

To: OmegaPhil <OmegaPhil@startmail.com>

Cc: 757348@bugs.debian.org, Cameron Norman <camerontnorman@gmail.com>

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

Date: Sun, 12 Oct 2014 18:49:32 +0200

[Message part 1 (text/plain, inline)]

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 that when systemd-shim calls cgmanager to MovePid/MovePidAbs
> > 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?
> 
> So, I think it should and it would. I omitted very important line from
> my previous log:
> 
> cgmanager: DEBUG per_ctrl_move_pid_main: 31385, memory - user.slice/user-1000.slice/session-c13.scope
> cgmanager: Found no cgroup entry for pid 31388 controller memory
> 
> The thing is -- cgmanager jumps out from the "all" loop after some
> problem with the "memory" controller. I do not know what to do with it
> yet.

I have applied a patch (attached) to cgmanager and everything seems to
work now. I will send it to cgmanager maintainer and upstream to ask if
it makes sense.

-- 
Marcin Szewczyk                       http://wodny.org
mailto:Marcin.Szewczyk@wodny.borg  <- remove b / usuń b
xmpp:wodny@ubuntu.pl                  xmpp:wodny@jabster.pl

[0001-check-enabled-column-when-parsing-proc-cgroups.patch (text/x-diff, attachment)]

Message #130 received at 757348@bugs.debian.org (full text, mbox, reply):

From: OmegaPhil <OmegaPhil@startmail.com>

To: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>

Cc: 757348@bugs.debian.org, Cameron Norman <camerontnorman@gmail.com>

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

Date: Sun, 12 Oct 2014 18:01:54 +0100

[Message part 1 (text/plain, inline)]

On 12/10/14 17:49, Marcin Szewczyk wrote:
> 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 that when systemd-shim calls cgmanager to MovePid/MovePidAbs
>>> 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?
>>
>> So, I think it should and it would. I omitted very important line from
>> my previous log:
>>
>> cgmanager: DEBUG per_ctrl_move_pid_main: 31385, memory - user.slice/user-1000.slice/session-c13.scope
>> cgmanager: Found no cgroup entry for pid 31388 controller memory
>>
>> The thing is -- cgmanager jumps out from the "all" loop after some
>> problem with the "memory" controller. I do not know what to do with it
>> yet.
> 
> I have applied a patch (attached) to cgmanager and everything seems to
> work now. I will send it to cgmanager maintainer and upstream to ask if
> it makes sense.

Awesome! If anything you want me to test/help with, just ping me.


-- 
Libre software on Github: https://github.com/OmegaPhil
FSF member #9442

[signature.asc (application/pgp-signature, attachment)]

Message #135 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>

To: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>

Cc: OmegaPhil <OmegaPhil@startmail.com>, 757348@bugs.debian.org

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

Date: Sun, 12 Oct 2014 10:04:17 -0700

[Message part 1 (text/plain, inline)]

El dom, 12 de oct 2014 a las 9:49 , Marcin Szewczyk 
<Marcin.Szewczyk@wodny.org> escribió:
> 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 that when systemd-shim calls cgmanager to 
>> MovePid/MovePidAbs
>>  > 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?
>> 
>>  So, I think it should and it would. I omitted very important line 
>> from
>>  my previous log:
>> 
>>  cgmanager: DEBUG per_ctrl_move_pid_main: 31385, memory - 
>> user.slice/user-1000.slice/session-c13.scope
>>  cgmanager: Found no cgroup entry for pid 31388 controller memory
>> 
>>  The thing is -- cgmanager jumps out from the "all" loop after some
>>  problem with the "memory" controller. I do not know what to do with 
>> it
>>  yet.
> 
> I have applied a patch (attached) to cgmanager and everything seems to
> work now. I will send it to cgmanager maintainer and upstream to ask 
> if
> it makes sense.

Oh gosh, I figured out why I am unaffected. This is in my kernel 
command line:

cgroup_enable=memory

It was there all along! Thanks for figuring this out.

Perhaps another good idea is to continue moving things and not just 
break out with a failure right away, then report failure once 
everything that can be moved is moved, you know?

Relevant code for that can be found here: 
https://github.com/cgmanager/cgmanager/blob/bfca08381096d1be6a952a520d9207d04a3d88cc/cgmanager.c#L215

Best regards,
--
Cameron Norman

[Message part 2 (text/html, inline)]

Message #140 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Cameron Norman <camerontnorman@gmail.com>

To: 757348@bugs.debian.org

Cc: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>, OmegaPhil <OmegaPhil@startmail.com>

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

Date: Sun, 12 Oct 2014 10:58:24 -0700

[Message part 1 (text/plain, inline)]

On Sun, 12 Oct 2014 18:49:32 +0200 Marcin Szewczyk 
<Marcin.Szewczyk@wodny.org> wrote:
> 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 that when systemd-shim calls cgmanager to 
MovePid/MovePidAbs
> > > 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?
> >
> > So, I think it should and it would. I omitted very important line 
from
> > my previous log:
> >
> > cgmanager: DEBUG per_ctrl_move_pid_main: 31385, memory - 
user.slice/user-1000.slice/session-c13.scope
> > cgmanager: Found no cgroup entry for pid 31388 controller memory
> >
> > The thing is -- cgmanager jumps out from the "all" loop after some
> > problem with the "memory" controller. I do not know what to do 
with it
> > yet.
>
> I have applied a patch (attached) to cgmanager and everything seems 
to
> work now. I will send it to cgmanager maintainer and upstream to ask 
if
> it makes sense.

Serge Hallyn is really good about quickly packaging up his new releases 
(he is maintainer upstream and in Debian (co-maintainer) and Ubuntu), 
so best bet is to just email him with the patch, or make a pull request 
on GitHub, whichever you prefer.

Also, can you review this additional fixup: 
https://github.com/cgmanager/cgmanager/pull/16 ?

Best regards,
--
Cameron Norman

[Message part 2 (text/html, inline)]

Message #151 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>

To: Cameron Norman <camerontnorman@gmail.com>

Cc: 757348@bugs.debian.org, OmegaPhil <OmegaPhil@startmail.com>

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

Date: Mon, 13 Oct 2014 14:40:27 +0200

On Sun, Oct 12, 2014 at 10:58:24AM -0700, Cameron Norman wrote:
> Serge Hallyn is really good about quickly packaging up his new releases (he
> is maintainer upstream and in Debian (co-maintainer) and Ubuntu), so best
> bet is to just email him with the patch, or make a pull request on GitHub,
> whichever you prefer.
> 
> Also, can you review this additional fixup:
> https://github.com/cgmanager/cgmanager/pull/16 ?

I have recompiled cgmanager with both patches. Everything works. I have
seen they have been applied upstream so I suppose now we can just wait
for an upload to unstable/testing.

-- 
Marcin Szewczyk                       http://wodny.org
mailto:Marcin.Szewczyk@wodny.borg  <- remove b / usuń b
xmpp:wodny@ubuntu.pl                  xmpp:wodny@jabster.pl

Message #156 received at 757348-close@bugs.debian.org (full text, mbox, reply):

From: Serge Hallyn <serge.hallyn@ubuntu.com>

To: 757348-close@bugs.debian.org

Subject: Bug#757348: fixed in cgmanager 0.33-2

Date: Tue, 14 Oct 2014 03:35:00 +0000

Source: cgmanager
Source-Version: 0.33-2

We believe that the bug you reported is fixed in the latest version of
cgmanager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 757348@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Serge Hallyn <serge.hallyn@ubuntu.com> (supplier of updated cgmanager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 14 Oct 2014 01:33:03 +0200
Source: cgmanager
Binary: cgmanager cgmanager-tests libcgmanager0 libcgmanager-dev
Architecture: source amd64 all
Version: 0.33-2
Distribution: unstable
Urgency: medium
Maintainer: Serge Hallyn <serge.hallyn@ubuntu.com>
Changed-By: Serge Hallyn <serge.hallyn@ubuntu.com>
Description:
 cgmanager  - Central cgroup manager daemon
 cgmanager-tests - Central cgroup manager daemon (tests)
 libcgmanager-dev - Central cgroup manager daemon (dev)
 libcgmanager0 - Central cgroup manager daemon (client library)
Closes: 757348
Changes:
 cgmanager (0.33-2) unstable; urgency=medium
 .
   * Cherrypick two upstream patches to ensure that 'movepid all' continues
     when a subsystem is not enabled.  (Closes: #757348)
Checksums-Sha1:
 922819cb05bcae88d7dd956bb18fffb41ad4072f 2052 cgmanager_0.33-2.dsc
 ed5ef7eed33f16158b471c69429251564e809957 11240 cgmanager_0.33-2.debian.tar.xz
 0d887dac71c1417f90b571089b1541f3dab4715f 77074 cgmanager_0.33-2_amd64.deb
 31d80f20875115cb8a7ed88a6f8b86f69bdd7d2c 13390 cgmanager-tests_0.33-2_all.deb
 cfbd4c7d7c3e5b73c6a37814006871aec1bd88a6 40320 libcgmanager0_0.33-2_amd64.deb
 1c3ca56bce38cede1b61d0222faa4003351b1eb0 10554 libcgmanager-dev_0.33-2_amd64.deb
Checksums-Sha256:
 ef482ada0c75c40ba7756acc75beb9ed3e9cd39670b039bbe9e6177fa5e7537f 2052 cgmanager_0.33-2.dsc
 6c81c1eb79c6c74f19c32feedd91b7be7f6df8376d5d81e9ce292989d77f25c4 11240 cgmanager_0.33-2.debian.tar.xz
 47d48ff84dd40982353ee710152b2a27024d4635f2e0219ec7edf25c320d4488 77074 cgmanager_0.33-2_amd64.deb
 9002de026c881b893d428a646f805318e422706dd386ad3077251322f18dc1c1 13390 cgmanager-tests_0.33-2_all.deb
 eba546082a66c5d1af2fad3bfa5bfb9e15e978231ef56d7a73d73b719e084dcb 40320 libcgmanager0_0.33-2_amd64.deb
 2ff2fda5a829dcd7d70ebc57814038f824c67e8278cde3ab3ce13621f889f0d6 10554 libcgmanager-dev_0.33-2_amd64.deb
Files:
 4ecbf03f8af2b2da3cf36762034b4563 2052 admin optional cgmanager_0.33-2.dsc
 a529b9a85e0f80650e2aa322a50b1335 11240 admin optional cgmanager_0.33-2.debian.tar.xz
 4065f0887c98d6ccac4e568353f88d90 77074 admin optional cgmanager_0.33-2_amd64.deb
 97983606b8dc02c29ba433105550000b 13390 admin optional cgmanager-tests_0.33-2_all.deb
 14609f6b99ae9794ec86868e3b311e28 40320 admin optional libcgmanager0_0.33-2_amd64.deb
 e42e4710a409ebafb6125477a038aabf 10554 libdevel optional libcgmanager-dev_0.33-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUPJfQAAoJEFaNMPMhshM9kfkQALBIPbgrLLhirpnITbVD/tAa
pj91RsjAt3TKbaAfaMxg2gIMeUjlUGI+GW4BNp1kcTzsHezSd16J7T2ZLL13qlLe
fsnvoEXK3ujwLWCnf6GNIJyvFV9+LPIQ8x5MwFQ/hfAg0p446SJSLyEefsbRsLlY
z9No6pKujzPJ9gpqCUjkf7uOuANMeIxqcwPYXTxWAvQ/mW+J61MobGcpWv92wsTF
8SpC4/CFhfu9y0ZECIOKjGYvtXPNO8SCR39ThLRSZr/B52eax9RIyaChQrtEBj6a
/ahMB4DcKlGhIJqYjQJfRuwvJ7aBa7iIkbNX1dfehbwNLrKnk4LVV/AByCmKgAfn
7l74j75iskv51lwWrfTd5ptHLB1GwhRwqwjjCfMa8o+Nkzgqcz9niUhz3HgQXiT+
qT+NKHk+35DMQ2w57id2NSEQLAJzkNFhhEPGuGNaAE7Nz99J8YvW+dE5UTdhaH1l
B9UvHduN01TKw9vLpTrBzzKgpf4WO03pde2JXDGOXlUkjRJkqCdxQKot6aL6/tIc
1w5wJdHfwy/VHn3ty5qTvRy7eLaA6o7DYUoYpvZcLIjsYDAF1cgw3YCKj9/iw0bm
795wvd8TozfaCIqf/tJzHAjqKz0VqLkWkYgy+hwbmDiFTgGetpjJYTy1s1imVQv2
jGbDgwO/7gYmCsYy+ZYT
=m4f+
-----END PGP SIGNATURE-----

Message #169 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Adam Borowski <kilobyte@angband.pl>

To: debian-devel@lists.debian.org, 757348@bugs.debian.org

Subject: Re: piece of mind

Date: Wed, 22 Oct 2014 01:18:38 +0200

[Sorry for slow response, testing this on one's main machine requires
dropping too much state...]  I should have CCed the bug earlier, doing this
now.

On Mon, Oct 20, 2014 at 08:37:04PM -0700, Cameron Norman wrote:
> > * the Utopia stack (restart, shutdown, suspend, hibernate, mounting USB
> >   drives, etc from GUI (with low-level tools like pm-utils working)).
> >   This is supposed to be handled by systemd-shim which doesn't currently
> >   work for me, but some folks report it being ok.
> 
> What versions (of shim and cgmgr) did you try it with? I thought these
> types of issues were fixed in Sid :/

I just retested, with current unstable (ie, 8-3 and 0.33-2).  Same results
as week ago (when shim was uploaded):

On lightdm screen, reboot/shutdown/etc are grayed out.
As a logged-in user:
* suspend/hibernate are _not_ grayed out (as they were some time ago), but
  show an error: "Failed to suspend session
  GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied"
* reboot/shutdown log me out instead, back to lightdm
I forgot to check mounting USB drives this time.


On the other hand, on a semi-fresh virtual machine (d-i beta 1), shim 8-3
started to work correctly.

-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable and Non-Discriminatory prices.

Message #182 received at 757348@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: 757348@bugs.debian.org

Subject: Not really fixed

Date: Wed, 10 Dec 2014 20:52:17 -0600

I'm still seeing this issue, and I have cgmanager 0.33-2 installed..

Message #187 received at 757348@bugs.debian.org (full text, mbox, reply):

From: vasos mitropoulos <noxelia@gmail.com>

To: 757348@bugs.debian.org

Subject: Debian jessie, same behaviour (AccessDenied)

Date: Fri, 26 Dec 2014 22:34:22 +0200

policykit-1                                                 0.105-8
 lightdm 1.10.3-3
 cgmanager 0.33-2

Message #194 received at 760281-close@bugs.debian.org (full text, mbox, reply):

From: Serge Hallyn <serge.hallyn@ubuntu.com>

To: 760281-close@bugs.debian.org

Subject: Bug#760281: fixed in cgmanager 0.36-1

Date: Thu, 12 Feb 2015 17:03:34 +0000

Source: cgmanager
Source-Version: 0.36-1

We believe that the bug you reported is fixed in the latest version of
cgmanager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 760281@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Serge Hallyn <serge.hallyn@ubuntu.com> (supplier of updated cgmanager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 11 Feb 2015 22:24:24 -0600
Source: cgmanager
Binary: cgmanager cgmanager-tests libcgmanager0 libcgmanager-dev
Architecture: source amd64 all
Version: 0.36-1
Distribution: unstable
Urgency: medium
Maintainer: Serge Hallyn <serge.hallyn@ubuntu.com>
Changed-By: Serge Hallyn <serge.hallyn@ubuntu.com>
Description:
 cgmanager  - Central cgroup manager daemon
 cgmanager-tests - Central cgroup manager daemon (tests)
 libcgmanager-dev - Central cgroup manager daemon (dev)
 libcgmanager0 - Central cgroup manager daemon (client library)
Closes: 760281 767468
Changes:
 cgmanager (0.36-1) unstable; urgency=medium
 .
   * New upstream release.
     - start in a clean mounts namespace (Closes: #760281, #767468)
   * add *list_keys* to symbols file
   * pass -c4 to dh_makeshlibs to catch missing smbols in the future
Checksums-Sha1:
 93181f6eddce3d289978f70b5052d1e87450ef9a 2052 cgmanager_0.36-1.dsc
 611f8da062bf8504df07d9ae8526d92bc227c801 428374 cgmanager_0.36.orig.tar.gz
 ff13af416b6ad0ab3ce31ea471fb736c9a975d4d 10600 cgmanager_0.36-1.debian.tar.xz
 bba9efc9473c0292c75ce676c50408731edfb9cd 78972 cgmanager_0.36-1_amd64.deb
 92d2953ddcb9d70065fa27a75c85611eb3dec4de 13806 cgmanager-tests_0.36-1_all.deb
 ce525b80b8432e6b30ef0a9ff65f8f8c49ba9726 40898 libcgmanager0_0.36-1_amd64.deb
 a2aa076fbf60d25663143069dc3396fe0d4ea3d1 10890 libcgmanager-dev_0.36-1_amd64.deb
Checksums-Sha256:
 b09a684963fe3e311924514e2d8e156fdfc38343e33ee2bd87bcf006df0e84d0 2052 cgmanager_0.36-1.dsc
 f4707f0130efb50ccd8a1900e7ae626c0631947528ce921a63b15ef848fb2a0d 428374 cgmanager_0.36.orig.tar.gz
 b38a50ee57bb945f81c233fdd2f39eb163ddcd671caf1558c2f6fd6bb47936e4 10600 cgmanager_0.36-1.debian.tar.xz
 fde26aaa8785efef5a9370d5039b6f6d96dfd02a7e9cde46419f59735944235b 78972 cgmanager_0.36-1_amd64.deb
 b8a42c3b39edc2a4a8d239b9a4243c3a2ee3a07bd02b218c613167d6e42f04b3 13806 cgmanager-tests_0.36-1_all.deb
 94c9d1fca1a9d355ed286393ea55e222441f0747b105b1b7c8c9c2b70bef8d9e 40898 libcgmanager0_0.36-1_amd64.deb
 fc9923fa79353c7c3a0588f0723b985f3a143079409413b30f447b207e15dd6d 10890 libcgmanager-dev_0.36-1_amd64.deb
Files:
 973017e8e6f089156df557312360a0d6 2052 admin optional cgmanager_0.36-1.dsc
 eaa1ead225b4cb3aa91111865faa6e35 428374 admin optional cgmanager_0.36.orig.tar.gz
 6a822c6e565a49fa44afd528f4b01de8 10600 admin optional cgmanager_0.36-1.debian.tar.xz
 1c18718eac2b1b95c7507f46dc670d7b 78972 admin optional cgmanager_0.36-1_amd64.deb
 761ddd91037be2c8a2c52dceb1987c64 13806 admin optional cgmanager-tests_0.36-1_all.deb
 82092dba6ed963e1a981ac8772ee2ad3 40898 admin optional libcgmanager0_0.36-1_amd64.deb
 0378a846957ef54cc5b7e69ee1ef0a35 10890 libdevel optional libcgmanager-dev_0.36-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU3NiuAAoJENFO8V2v4RNHQ4oP/RXv1RmpWiDiR68SLRhWZi9E
XCLqdnVgB+PHZoowgOfG4hPLprn0wXIv/tMieYJ4W+19YU0cIvs9/yUvA8okMiF2
1AJhWaymb+GGLKiCBwao+hnNVEZFrsr6sDlHebzRFgGZAi/MXReWv5LkHVpxMGQE
tPv0f557RvT3Smr3P/axAUCmQnj177GZ/VIi2Qfp/wpc3k0Wj2NQHFe9zO8Rt8wN
Ip8zLlkaoUNt+lGvTVROwpOWQCvnBhK2tEEcXBxdehClLcW0egbTIRgF2XD5nrm/
fhOI9Nqeg8C2Ru3ROPsE16TD4DgjfvjYsMnal8qMZnoMKbugxZj6dWjh+zzXuRYB
XcSEPhAgskjG+U0IImURqFk0XONuUihd6mEYls9usyio7QznFugbSQi/Fspysra+
WMDxCwS6HOeJvB5b1+pCxr2tasBV9cv9TV0fDs+UVAPPMq8SaFw9QBDl+igf1pkx
qa/yV95FHzmFHvd7dOuYZcSIB+q1Acd7Wq8b/H1PElSTd+bBNsoBWhuzt/sHf4gX
S/Ty6AXmIQ/4REpVMKSaTmiTZEh6yGp042hqcJfxIidDzwf1HoSTatrN8jvtP+xB
sxKH1Xhe8ebcLDTOa4+Ek4H9R60PxX/cTOiXuEaK8i7jJjFJ1IGlFQ+OhjFG0x/H
mbbSvvXmN8g+QVFgRe6U
=H6sw
-----END PGP SIGNATURE-----

Message #199 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Debian Bug Tracking System <757348@bugs.debian.org>

Subject: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Fri, 13 Feb 2015 17:12:50 +0100

Control: reopen -1
Control: found -1 0.36-1

The problem was fixed some time ago, but reappeared. With lightdm,
the 4 operations are greyed out.

Note: I rebooted after the upgrade.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages cgmanager depends on:
ii  init-system-helpers  1.22
ii  libc6                2.19-15
ii  libcgmanager0        0.36-1
ii  libdbus-1-3          1.8.16-1
ii  libnih-dbus1         1.0.3-4.3
ii  libnih1              1.0.3-4.3

cgmanager recommends no packages.

cgmanager suggests no packages.

-- no debconf information

Message #210 received at 757348@bugs.debian.org (full text, mbox, reply):

From: OmegaPhil <OmegaPhil@startmail.com>

To: 757348@bugs.debian.org

Subject: [cgmanager] RE: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Fri, 13 Feb 2015 16:18:42 +0000

[Message part 1 (text/plain, inline)]

Package: cgmanager
Version: 0.36-1

Have confirmed this works in my VM, so it isn't affecting me this time
(not yet needed to restart this main machine).


--- System information. ---
Architecture: amd64
Kernel:       Linux 3.16.0-4-amd64

Debian Release: 8.0
  990 testing         10.1.0.3
  500 unstable        10.1.0.3
  500 quodlibet-unstable 10.1.0.3
    1 experimental    10.1.0.3

--- Package information. ---
Depends                   (Version) | Installed
===================================-+-============
libc6                     (>= 2.15) |
libcgmanager0             (>= 0.28) |
libdbus-1-3             (>= 1.2.16) |
libnih-dbus1             (>= 1.0.0) |
libnih1                  (>= 1.0.0) |
init-system-helpers      (>= 1.18~) |


Package's Recommends field is empty.

Package's Suggests field is empty.

[signature.asc (application/pgp-signature, attachment)]

Message #215 received at 757348@bugs.debian.org (full text, mbox, reply):

From: Serge Hallyn <serge.hallyn@ubuntu.com>

To: Vincent Lefevre <vincent@vinc17.net>, 757348@bugs.debian.org

Subject: Re: Bug#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm

Date: Fri, 13 Feb 2015 19:50:06 +0000

Thanks for the report, Vincent.  I see the cause of the bug.  The fix is
now upstream, and I'll get it into sid asap.

Message #220 received at 757348-close@bugs.debian.org (full text, mbox, reply):

From: Serge Hallyn <serge.hallyn@ubuntu.com>

To: 757348-close@bugs.debian.org

Subject: Bug#757348: fixed in cgmanager 0.36-2

Date: Sat, 14 Feb 2015 01:33:30 +0000

Source: cgmanager
Source-Version: 0.36-2

We believe that the bug you reported is fixed in the latest version of
cgmanager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 757348@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Serge Hallyn <serge.hallyn@ubuntu.com> (supplier of updated cgmanager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 13 Feb 2015 13:48:40 -0600
Source: cgmanager
Binary: cgmanager cgmanager-tests libcgmanager0 libcgmanager-dev
Architecture: source amd64 all
Version: 0.36-2
Distribution: unstable
Urgency: medium
Maintainer: Serge Hallyn <serge.hallyn@ubuntu.com>
Changed-By: Serge Hallyn <serge.hallyn@ubuntu.com>
Description:
 cgmanager  - Central cgroup manager daemon
 cgmanager-tests - Central cgroup manager daemon (tests)
 libcgmanager-dev - Central cgroup manager daemon (dev)
 libcgmanager0 - Central cgroup manager daemon (client library)
Closes: 757348
Changes:
 cgmanager (0.36-2) unstable; urgency=medium
 .
   * import upstream patch to bind-mount / into new root.  (Closes: #757348)
   * import upstream patch to bind-mount /run into new root so that on
     sysvinit the /run/cgmanager.pid file shows up on the host.
Checksums-Sha1:
 021014afcd0350b6684078cd3f4ab961fe140dd8 2052 cgmanager_0.36-2.dsc
 ae11f2590b18ab62d181b0cbc62b093cfed891be 11628 cgmanager_0.36-2.debian.tar.xz
 66a84db1f626a3c09b7f539171fcf360e68ca36f 79426 cgmanager_0.36-2_amd64.deb
 5d61f0af922aa310d272949c68f780ce2ba64d18 13926 cgmanager-tests_0.36-2_all.deb
 602098852e3dd75a082c59e044a0081bdb858c18 40956 libcgmanager0_0.36-2_amd64.deb
 4a7c7cc85adf5a7527a1522b80be9af044d4d9e0 10994 libcgmanager-dev_0.36-2_amd64.deb
Checksums-Sha256:
 9e350ad67bd46d3f2a9feb882a94d61db64ef8c5df053308728d4dae938b013f 2052 cgmanager_0.36-2.dsc
 1ef15d2a3b55f3969518fa579eb0b175c5e59b2ff25fd8621ef6abf1ab06c0a3 11628 cgmanager_0.36-2.debian.tar.xz
 92f40f69a2fe744572cc211902ff57f19c0da5f3c64708ac93e13fef6a141bce 79426 cgmanager_0.36-2_amd64.deb
 b292b39d8471e2f503d9143623316fbd40f9825f10f08369eb780b294c49e77d 13926 cgmanager-tests_0.36-2_all.deb
 cd7cb9b2bb72f699f7e5f09d7916b39372ff9f79996b2d68ea5b719b11af27c5 40956 libcgmanager0_0.36-2_amd64.deb
 db075d70a658bee17971914ecc7977f6dae1f1e2d73bcb3e308be5c97d258892 10994 libcgmanager-dev_0.36-2_amd64.deb
Files:
 d18603340256cb52f09b7cc28c62e47d 2052 admin optional cgmanager_0.36-2.dsc
 e06d7cca82c166dbcdb2e948187cbbf0 11628 admin optional cgmanager_0.36-2.debian.tar.xz
 7cd34a413822079ebb965cc10fe7567d 79426 admin optional cgmanager_0.36-2_amd64.deb
 e551a21f6a66338e49a0953b6b9518e2 13926 admin optional cgmanager-tests_0.36-2_all.deb
 84e75ecc84ddb7185b0a8ced0efe0d50 40956 admin optional libcgmanager0_0.36-2_amd64.deb
 9740766fa2366b1fbb49c0af35a69fa9 10994 libdevel optional libcgmanager-dev_0.36-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU3qJnAAoJEFaNMPMhshM9tEMP/2fUI4mYTijMJpO3nJ34tbJ0
rjZECDSiRSoa29u/kbNI/7enilyMzaYcy2XqfNE7w16ppA0qxxDRo3jZmbr1Tx/1
PL8q8wFJvFAcZJa1P2ziIzANCaFoZV7DvPlgSWEiv1SE6H1HSVJAVgOlD9hf44o+
zkFifwCgjhdgGVIcKd6K5rL/ZGT4BFIm3nq1P6HLTJ34y/6xyZvq/zklBQMuVTKr
NNKwg39tHttaGxV+CyYJYTx3wkWtDwoQugJOtXREcxRm1FK4423QH5jsJPm1NLzi
qCTsko3/icWDPQNTi4DrsaGMxd2NG/aEGQ2CGUuNh3e/dmn9ZqjrocCjANgH0Fy1
lWLFZWOsUTRs5JNKQQy8Vb3c2wm2TD/u9kMdArAHQCPyHq+13G4uva+DzPfoYZHg
Ltjfn7isDLNHngabIvo9Y6HDBTD1aW34mGe8zarSKvbq9XZGNhM7hxo6sEMBInGh
1XkMzaSw6Ywe8M2mqYbsNlrdMeKaJKDZ88dyqQxjmJnBaCgpq9pYXKopqFEDNpQf
0MkXh+QuYe1XGZ25lvr9l9jMG/ZuL54Fdcsm5l7oMchK0NdpuBcqDhMaiNBFvo0o
z/n+blhimtQnP+Fm/QHLAh2cO5qoSnU4tmmkVvno3oZQeyId8GAfE9ZE73wpVTlO
p8fY0x92UmJmGgvv6kG0
=hXag
-----END PGP SIGNATURE-----

Message #249 received at 757348-close@bugs.debian.org (full text, mbox, reply):

From: Serge Hallyn <serge.hallyn@ubuntu.com>

To: 757348-close@bugs.debian.org

Subject: Bug#757348: fixed in cgmanager 0.33-2+deb8u2

Date: Mon, 16 Mar 2015 21:33:50 +0000

Source: cgmanager
Source-Version: 0.33-2+deb8u2

We believe that the bug you reported is fixed in the latest version of
cgmanager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 757348@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Serge Hallyn <serge.hallyn@ubuntu.com> (supplier of updated cgmanager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 14 Mar 2015 23:37:07 -0500
Source: cgmanager
Binary: cgmanager cgmanager-tests libcgmanager0 libcgmanager-dev
Architecture: all source
Version: 0.33-2+deb8u2
Distribution: testing-proposed-updates
Urgency: medium
Maintainer: Serge Hallyn <serge.hallyn@ubuntu.com>
Changed-By: Serge Hallyn <serge.hallyn@ubuntu.com>
Closes: 757348
Description: 
 cgmanager  - Central cgroup manager daemon
 cgmanager-tests - Central cgroup manager daemon (tests)
 libcgmanager0 - Central cgroup manager daemon (client library)
 libcgmanager-dev - Central cgroup manager daemon (dev)
Changes:
 cgmanager (0.33-2+deb8u2) testing-proposed-updates; urgency=medium
 .
   * Cherrypick patches to run cgmanager in a private namespace to prevent
     host mounts from being pinned.  (Closes: #757348)
   * libcgmanager0.symbols: add list_keys
   * debian/rules: add dh_makeshlibs -- -c4 to fail when symbols are not
     added to libcgmangaer0.symbols.
Checksums-Sha1: 
 2d94e1f8f93a94df6e712c589723253a7040f210 2080 cgmanager_0.33-2+deb8u2.dsc
 4078db08c776dd9e1c531cb76266b95a615e8c1a 15832 cgmanager_0.33-2+deb8u2.debian.tar.xz
 4660e87848e0bb98788e37d48f4ea9776292d2bc 13754 cgmanager-tests_0.33-2+deb8u2_all.deb
Checksums-Sha256: 
 b4f42f10aef7c05c3b6a9594e42b94a100ab72e49f846f7601a7c04e33be480f 2080 cgmanager_0.33-2+deb8u2.dsc
 77c4197be63642d0573a2ae2565cdc5269e58a673b43bd424dbd08aa7a0f8772 15832 cgmanager_0.33-2+deb8u2.debian.tar.xz
 c7644639676b0bd7855e8acf4b8c06c82c0710198bcd896ef678198d49bdd2a4 13754 cgmanager-tests_0.33-2+deb8u2_all.deb
Files: 
 68ca30c5c455be7942401daf8a84d0a9 2080 admin optional cgmanager_0.33-2+deb8u2.dsc
 0eb188d6df1c998acecfb0270fceb549 15832 admin optional cgmanager_0.33-2+deb8u2.debian.tar.xz
 ab6f49543e3eaecdf5ace10e6ee1a1f3 13754 admin optional cgmanager-tests_0.33-2+deb8u2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVBzmUAAoJEINAGjCxzeWPQ8QP/06f2tnV/PefLOURdv1C4xwa
lFsK9ygWhLaea+ppaxfmKYCqkoRWXMUZMkXNV5fxW33qWpoG9i7S4+J1vkiOb2eB
46vskEWkOKboIAB0h1a+e9YHwX7CrAyi+KU6ICdhaMi6igY4HUBB9mSNfz59av7I
ddCOshgd8ITmWmsmPI50xS0nozoEoKUD6BVJuUNc3vXTrY4owYxOHtx0aAZ81zlH
pN5+xNBaAY49MQPUntonDGc/HD6Wh7ttuARuj5EdO5qp0wlp2xJ0xcrjU9DTBbd3
4oNje/y+CLHxUML7iQqgateQfyhUEF+46qpUmADB7krUw+uugdVYZ3qT5syJ6uc8
ywUQkvoIhoQ5S+H7hE5H6Wx8X4JRZVPzRxQ19nsuHphIO7dDDIQS2hVqwjfEzgbr
GuAQfD7OFLOI73FOUuwBoSS3lAc/JsBS4w3KXuWYEe+QOj0xwPL4YLgq5l9noimT
vTKRumYQVW+HpxRHrjod+8aBlbFEC3L0B/ZPx9IU3M5JbaJpam90BjCWl15f1n9G
4o1OJUzaVxJPf/eTYQjIqPB3b0jmNdHY1MvyFyfBO2lI4/T28xbXU5vIoXePlLp4
YCiEv8VWjaDo7j5ZHQ2dPn6BLsFmW7/Ca857i03dEUZHRShOEJ5b3ZWAKw/Deaak
yBjjqTpREu9aOvCZc74M
=hcga
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.