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
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,
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:
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
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
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
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
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
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.
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
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.
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
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 -
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
14 matches
Mail list logo
