Bug#787542: marked as done (libudev1-udeb depends on missing libcap2)

Your message dated Thu, 11 Jun 2015 10:25:59 + with message-id e1z2zgn-0002lr...@franck.debian.org and subject line Bug#787542: fixed in systemd 220-6 has caused the Debian Bug report #787542, regarding libudev1-udeb depends on missing libcap2 to be marked as done. This means that you claim

Bug#770135: systemd: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted

After upgrade to Jessie 8.1 problem still exist ii systemd215-17+deb8u1 systemctl restart systemd-logind.service still have to manually restart the services ___ Pkg-systemd-maintainers mailing list

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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

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

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 -

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #746151 (http://bugs.debian.org/746151) # Bug title: systemd: daemon-reload+reload

could you look at http://bugs.debian.org/788380 part of it involves systemd-user

Hi Michael, Could you take a look at http://bugs.debian.org/788380 and see if it could be helped along ? -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/

Processed: tagging 783509

Processing commands for cont...@bugs.debian.org: tags 783509 + pending Bug #783509 [systemd] tmp.mount activated accidentally via bind mount Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 783509:

Processed: severity of 783509 is important

Processing commands for cont...@bugs.debian.org: severity 783509 important Bug #783509 [systemd] tmp.mount activated accidentally via bind mount Severity set to 'important' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 783509:

Processing of systemd_220-6_amd64.changes

systemd_220-6_amd64.changes uploaded successfully to localhost along with the files: systemd_220-6.dsc systemd_220-6.debian.tar.xz libnss-myhostname_220-6_amd64.deb libnss-mymachines_220-6_amd64.deb libpam-systemd_220-6_amd64.deb libsystemd-daemon-dev_220-6_amd64.deb