Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-07-05 Thread Yaroslav Molochko
works for me! Thank you very much!

2015-07-03 18:13 GMT+08:00 Michael Biebl bi...@debian.org:
 Control: forwarded -1 https://github.com/systemd/systemd/issues/451

 Hi Jessie, hi Yaroslav!

 Am 12.06.2015 um 17:21 schrieb Michael Biebl:
 Am 11.06.2015 um 20:44 schrieb Jessica Frazelle:
 Can you reboot,run
  ls -la /sys/class/drm
 suspend/resume and run again
  ls -la /sys/class/drm

 Ok, let's retry this again:

 for i in /sys/class/drm/*/status; do echo $i; cat $i; done

 Please run that before and after suspend.

 This particular issue is supposed to be fixed in v221.
 Can you please test the latest version from unstable and confirm that?

 Cheers,
 Michael


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


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-07-03 Thread Michael Biebl
Control: forwarded -1 https://github.com/systemd/systemd/issues/451

Hi Jessie, hi Yaroslav!

Am 12.06.2015 um 17:21 schrieb Michael Biebl:
 Am 11.06.2015 um 20:44 schrieb Jessica Frazelle:
 Can you reboot,run
  ls -la /sys/class/drm
 suspend/resume and run again
  ls -la /sys/class/drm
 
 Ok, let's retry this again:
 
 for i in /sys/class/drm/*/status; do echo $i; cat $i; done
 
 Please run that before and after suspend.

This particular issue is supposed to be fixed in v221.
Can you please test the latest version from unstable and confirm that?

Cheers,
Michael


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



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-07-03 Thread Debian Bug Tracking System
Processing control commands:

 forwarded -1 https://github.com/systemd/systemd/issues/451
Bug #788400 [systemd] systemd-logind only fires suspend on lid close once even 
though it sees the event
Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/451'.

-- 
788400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-12 Thread Michael Biebl
Am 11.06.2015 um 20:44 schrieb Jessica Frazelle:
 Can you reboot,run
  ls -la /sys/class/drm
 suspend/resume and run again
  ls -la /sys/class/drm

Ok, let's retry this again:

for i in /sys/class/drm/*/status; do echo $i; cat $i; done

Please run that before and after suspend.




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



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
 systemd-inhibit
 Who: NetworkManager (UID 0/root, PID 693/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

1 inhibitors listed.

On Thu, Jun 11, 2015 at 3:16 AM, Michael Biebl bi...@debian.org wrote:
 Control: tags -1 moreinfo

 Am 11.06.2015 um 02:13 schrieb jessie:

 And the output of the systemd-logind.service, as you can see it fires 
 `suspend` on the first lid close but never on any after the very first lid 
 close, it is very odd, it clearly sees the event:

 ```
 -- Logs begin at Wed 2015-06-10 16:49:40 PDT, end at Wed 2015-06-10 17:05:35 
 PDT. --
 Jun 10 16:49:41 debian systemd[1]: Starting Login Service...
 Jun 10 16:49:41 debian systemd-logind[559]: New seat seat0.
 Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
 /dev/input/event4 (Power But
 Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
 /dev/input/event9 (Video Bus
 Jun 10 16:49:41 debian systemd[1]: Started Login Service.
 Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
 /dev/input/event2 (Power But
 Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
 /dev/input/event1 (Lid Switc
 Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
 /dev/input/event3 (Sleep But
 Jun 10 16:49:47 debian systemd-logind[559]: New session 1 of user jessie.
 Jun 10 16:52:18 debian systemd-logind[559]: Lid closed.
 Jun 10 16:52:18 debian systemd-logind[559]: Suspending...
 Jun 10 16:52:31 debian systemd-logind[559]: Lid opened.
 Jun 10 16:52:31 debian systemd-logind[559]: Operation finished.
 Jun 10 16:54:44 debian systemd-logind[559]: Lid closed.
 Jun 10 16:54:57 debian systemd-logind[559]: Lid opened.
 Jun 10 16:56:48 debian systemd-logind[559]: Lid closed.
 Jun 10 16:56:51 debian systemd-logind[559]: Lid opened.
 Jun 10 16:56:57 debian systemd-logind[559]: Lid closed.
 Jun 10 16:57:06 debian systemd-logind[559]: Lid opened.
 Jun 10 16:58:33 debian systemd-logind[559]: Lid closed.
 Jun 10 16:58:39 debian systemd-logind[559]: Lid opened.

 What's the output of systemd-inhibit?

 Maybe some application is block the suspend request.

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




-- 


Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
Here are the NetworkManager.service logs, it sees the first suspend
and sleeps but it is not even getting the others


-- Logs begin at Thu 2015-06-11 09:30:01 PDT, end at Thu 2015-06-11
09:47:32 PDT. -- Jun 11 09:30:02 debian systemd[1]: Starting Network
Manager... -- Subject: Unit NetworkManager.service has begun start-up
-- Defined-By: systemd -- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit
NetworkManager.service has begun starting up. Jun 11 09:30:02 debian
NetworkManager[693]: NetworkManager (version 1.0.2) is starting... Jun
11 09:30:02 debian NetworkManager[693]: Read config:
/etc/NetworkManager/NetworkManager.conf Jun 11 09:30:02 debian
NetworkManager[693]: WEXT support is enabled Jun 11 09:30:02 debian
NetworkManager[693]: init! Jun 11 09:30:02 debian NetworkManager[693]:
update_system_hostname Jun 11 09:30:02 debian NetworkManager[693]:
interface-parser: parsing file /etc/network/interfaces Jun 11 09:30:02
debian NetworkManager[693]: interface-parser: source line includes
interfaces file(s) /etc/network/interfaces.d/* Jun 11 09:30:02 debian
NetworkManager[693]: interfaces file /etc/network/interfaces.d/*
doesn't exist Jun 11 09:30:02 debian NetworkManager[693]:
interface-parser: finished parsing file /etc/network/interfaces Jun 11
09:30:02 debian NetworkManager[693]: guessed connection type (eth0) =
802-3-ethernet Jun 11 09:30:02 debian NetworkManager[693]:
update_connection_setting_from_if_block: name:eth0,
type:802-3-ethernet, id:Ifupdown (eth0), uuid:
681b428f-beaf-8932-dce4-687ed5bae28e Jun 11 09:30:02 debian
NetworkManager[693]: adding eth0 to connections Jun 11 09:30:02 debian
NetworkManager[693]: adding iface eth0 to eni_ifaces Jun 11 09:30:02
debian NetworkManager[693]: autoconnect Jun 11 09:30:02 debian
NetworkManager[693]: management mode: unmanaged Jun 11 09:30:02 debian
NetworkManager[693]: devices added (path:
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/wlan0, iface:
wlan0) Jun 11 09:30:02 debian NetworkManager[693]: device added (path:
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/wlan0, iface:
wlan0): no ifupdown configuration found. Jun 11 09:30:02 debian
NetworkManager[693]: devices added (path: /sys/devices/virtual/net/lo,
iface: lo) Jun 11 09:30:02 debian NetworkManager[693]: device added
(path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown
configuration found. Jun 11 09:30:02 debian NetworkManager[693]: end
_init. Jun 11 09:30:02 debian NetworkManager[693]: Loaded plugin
ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the
NetworkManager mailing list. Jun 11 09:30:02 debian
NetworkManager[693]: Loaded plugin keyfile: (c) 2007 - 2015 Red Hat,
Inc. To report bugs please use the NetworkManager mailing list. Jun 11
09:30:02 debian NetworkManager[693]: (11672832) ... get_connections.
Jun 11 09:30:02 debian NetworkManager[693]: (11672832) ...
get_connections (managed=false): return empty list. Jun 11 09:30:02
debian NetworkManager[693]: keyfile: new connection
/etc/NetworkManager/system-connections/DockerEng_Slow
(b562ec97-fec0-4b24-bf7a-8812fe97ee8b,DockerEng_Slow) Jun 11
09:30:02 debian NetworkManager[693]: keyfile: new connection
/etc/NetworkManager/system-connections/Not in Range
(1436f8b2-524c-490c-9b4c-72b8cfd0005c,Not in Range) Jun 11 09:30:02
debian NetworkManager[693]: get unmanaged devices count: 0 Jun 11
09:30:02 debian NetworkManager[693]: monitoring kernel firmware
directory '/lib/firmware'. Jun 11 09:30:02 debian NetworkManager[693]:
monitoring ifupdown state file '/run/network/ifstate'. Jun 11 09:30:02
debian NetworkManager[693]: rfkill1: found WiFi radio killswitch (at
/sys/devices/pci:00/:00:1c.3/:02:00.0/ieee80211/phy0/rfkill1)
(driver wl) Jun 11 09:30:02 debian NetworkManager[693]: WiFi hardware
radio set enabled Jun 11 09:30:02 debian NetworkManager[693]: WWAN
hardware radio set enabled Jun 11 09:30:02 debian NetworkManager[693]:
Loaded device plugin:
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin:
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so
Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin:
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so
Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin:
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin:
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-team.so
Jun 11 09:30:02 debian NetworkManager[693]: WiFi enabled by radio
killswitch; enabled by state file Jun 11 09:30:02 debian
NetworkManager[693]: WWAN enabled by radio killswitch; enabled by
state file Jun 11 09:30:02 debian NetworkManager[693]: WiMAX enabled
by radio killswitch; enabled by state file Jun 11 09:30:02 debian
NetworkManager[693]: Networking is enabled by state file Jun 11
09:30:02 debian NetworkManager[693]: (lo): link 

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 18:44 schrieb Jessica Frazelle:
  systemd-inhibit
  Who: NetworkManager (UID 0/root, PID 693/NetworkManager)
 What: sleep
  Why: NetworkManager needs to turn off networks
 Mode: delay
 
 1 inhibitors listed.

Ok, that looks fine.



Do you have an external monitor connected?
What happens if you set the following in logind.conf
HandleLidSwitchDocked=suspend
and run systemctl restart systemd-logind ?

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



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 19:06 schrieb Jessica Frazelle:
 No I don't have an external monitor, I also reproduced this on a
 ubuntu 15.04 machine and a machine with a commpletely fresh install of
 debian stretch with gnome.

I guess we need a more verbose debug log then.
Please boot with systemd.log_level=debug on the kernel command line, and
then attach the log from journalctl -u systemd-logind.service


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



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
will do!

On Thu, Jun 11, 2015 at 10:29 AM, Michael Biebl bi...@debian.org wrote:
 Am 11.06.2015 um 19:06 schrieb Jessica Frazelle:
 No I don't have an external monitor, I also reproduced this on a
 ubuntu 15.04 machine and a machine with a commpletely fresh install of
 debian stretch with gnome.

 I guess we need a more verbose debug log then.
 Please boot with systemd.log_level=debug on the kernel command line, and
 then attach the log from journalctl -u systemd-logind.service


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




-- 


Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
ok confirmed, it was HandleLidSwitchDocked=suspend, it just needed a
system reboot to register the change i guess restarting logind doesnt
do that

On Thu, Jun 11, 2015 at 10:43 AM, Jessica Frazelle m...@jessfraz.com wrote:
 so weird it is working now... and the debug is the only line I changed...



 On Thu, Jun 11, 2015 at 10:35 AM, Jessica Frazelle m...@jessfraz.com wrote:
 will do!

 On Thu, Jun 11, 2015 at 10:29 AM, Michael Biebl bi...@debian.org wrote:
 Am 11.06.2015 um 19:06 schrieb Jessica Frazelle:
 No I don't have an external monitor, I also reproduced this on a
 ubuntu 15.04 machine and a machine with a commpletely fresh install of
 debian stretch with gnome.

 I guess we need a more verbose debug log then.
 Please boot with systemd.log_level=debug on the kernel command line, and
 then attach the log from journalctl -u systemd-logind.service


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




 --


 Jessie Frazelle
 4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
 pgp.mit.edu



 --


 Jessie Frazelle
 4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
 pgp.mit.edu



-- 


Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 19:49 schrieb Jessica Frazelle:
 ok confirmed, it was HandleLidSwitchDocked=suspend, it just needed a
 system reboot to register the change i guess restarting logind doesnt
 do that

So logind believes your system is docked, probably because it detected a
second graphics device.

Can you please still attach the debug log.


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



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 20:04 schrieb Jessica Frazelle:
 attached here

Ok, two things:

If you suspend/resume/suspend within 90secs, systemd will ignore the 2n
suspend request. That's this line:

 Jun 11 10:42:17 debian systemd-logind[706]: Ignoring lid switch
request, system startup or resume too close.


Second, logind indeed believes you have multiple graphics devices attached:

 Jun 11 10:42:17 debian systemd-logind[706]: Multiple (3) displays
connected.


Can you reboot,run
 ls -la /sys/class/drm
suspend/resume and run again
 ls -la /sys/class/drm


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



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
jessie at debian in ~
$ ls -la /sys/class/drm
total 0
drwxr-xr-x  2 root root0 Jun 11 11:39 .
drwxr-xr-x 51 root root0 Jun 11 11:39 ..
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0 -
../../devices/pci:00/:00:02.0/drm/card0
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0-DP-1 -
../../devices/pci:00/:00:02.0/drm/card0/card0-DP-1
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0-eDP-1 -
../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0-HDMI-A-1 -
../../devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1
lrwxrwxrwx  1 root root0 Jun 11 11:39 controlD64 -
../../devices/pci:00/:00:02.0/drm/controlD64
lrwxrwxrwx  1 root root0 Jun 11 11:39 renderD128 -
../../devices/pci:00/:00:02.0/drm/renderD128
-r--r--r--  1 root root 4096 Jun 11 11:39 version

CLOSE LID
after resume...

jessie at debian in ~
$ ls -la /sys/class/drm
total 0
drwxr-xr-x  2 root root0 Jun 11 11:39 .
drwxr-xr-x 51 root root0 Jun 11 11:39 ..
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0 -
../../devices/pci:00/:00:02.0/drm/card0
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0-DP-1 -
../../devices/pci:00/:00:02.0/drm/card0/card0-DP-1
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0-eDP-1 -
../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1
lrwxrwxrwx  1 root root0 Jun 11 11:39 card0-HDMI-A-1 -
../../devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1
lrwxrwxrwx  1 root root0 Jun 11 11:39 controlD64 -
../../devices/pci:00/:00:02.0/drm/controlD64
lrwxrwxrwx  1 root root0 Jun 11 11:39 renderD128 -
../../devices/pci:00/:00:02.0/drm/renderD128
-r--r--r--  1 root root 4096 Jun 11 11:39 version


On Thu, Jun 11, 2015 at 11:30 AM, Michael Biebl bi...@debian.org wrote:
 Am 11.06.2015 um 20:04 schrieb Jessica Frazelle:
 attached here

 Ok, two things:

 If you suspend/resume/suspend within 90secs, systemd will ignore the 2n
 suspend request. That's this line:

 Jun 11 10:42:17 debian systemd-logind[706]: Ignoring lid switch
 request, system startup or resume too close.


 Second, logind indeed believes you have multiple graphics devices attached:

 Jun 11 10:42:17 debian systemd-logind[706]: Multiple (3) displays
 connected.


 Can you reboot,run
  ls -la /sys/class/drm
 suspend/resume and run again
  ls -la /sys/class/drm


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




-- 


Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-10 Thread jessie
Package: systemd
Version: 220-5
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-rc7-hackers-of-the-world-unite (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages systemd depends on:
ii  adduser 3.113+nmu3
ii  libacl1 2.2.52-2
ii  libapparmor12.9.2-3
ii  libaudit1   1:2.4.2-1
ii  libblkid1   2.26.2-6
ii  libc6   2.19-18
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2
ii  libkmod220-1
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libmount1   2.26.2-6
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 220-5
ii  mount   2.26.2-6
ii  sysv-rc 2.88dsf-59.2
ii  udev220-5
ii  util-linux  2.26.2-6

Versions of packages systemd recommends:
pn  dbusnone
pn  libpam-systemd  none

Versions of packages systemd suggests:
pn  systemd-ui  none

-- no debconf information

The following is my /etc/systemd/logind.conf:

```
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
HandlePowerKey=suspend
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=suspend
#HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
```

And the output of the systemd-logind.service, as you can see it fires `suspend` 
on the first lid close but never on any after the very first lid close, it is 
very odd, it clearly sees the event:

```
-- Logs begin at Wed 2015-06-10 16:49:40 PDT, end at Wed 2015-06-10 17:05:35 
PDT. --
Jun 10 16:49:41 debian systemd[1]: Starting Login Service...
Jun 10 16:49:41 debian systemd-logind[559]: New seat seat0.
Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
/dev/input/event4 (Power But
Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
/dev/input/event9 (Video Bus
Jun 10 16:49:41 debian systemd[1]: Started Login Service.
Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
/dev/input/event2 (Power But
Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
/dev/input/event1 (Lid Switc
Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on 
/dev/input/event3 (Sleep But
Jun 10 16:49:47 debian systemd-logind[559]: New session 1 of user jessie.
Jun 10 16:52:18 debian systemd-logind[559]: Lid closed.
Jun 10 16:52:18 debian systemd-logind[559]: Suspending...
Jun 10 16:52:31 debian systemd-logind[559]: Lid opened.
Jun 10 16:52:31 debian systemd-logind[559]: Operation finished.
Jun 10 16:54:44 debian systemd-logind[559]: Lid closed.
Jun 10 16:54:57 debian systemd-logind[559]: Lid opened.
Jun 10 16:56:48 debian systemd-logind[559]: Lid closed.
Jun 10 16:56:51 debian systemd-logind[559]: Lid opened.
Jun 10 16:56:57 debian systemd-logind[559]: Lid closed.
Jun 10 16:57:06 debian systemd-logind[559]: Lid opened.
Jun 10 16:58:33 debian systemd-logind[559]: Lid closed.
Jun 10 16:58:39 debian systemd-logind[559]: Lid opened.
```

[EXTENDED]   /lib/systemd/system/systemd-timesyncd.service - 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[EXTENDED]   /lib/systemd/system/rc-local.service - 
/lib/systemd/system/rc-local.service.d/wait-online.conf

2 overridden configuration files found.

# UNCONFIGURED FSTAB FOR BASE SYSTEM

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers