I created an upstream pull request at
https://github.com/systemd/systemd/pull/1100
All reporters: it would be nice if you could confirm the fix by editing
/lib/udev/rules.d/70-power-switch.rules and adding the line
SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="* WMI hotkeys", TAG
Thanks Andreas, well spotted! This is the same issue as for the original
reporter, inode77, and Kevin:
Mai 04 08:47:33 damm-xyz1 kernel: input: HP WMI hotkeys as
/devices/virtual/input/input17
[...]
Mai 04 08:47:37 damm-xyz1 systemd-logind[853]: Watching system buttons on
/dev/input/event2
I have the same problem on an HP EliteBook 8560w (with AMD GPU running
fglrx driver) in an HP Docking Station.
In this setup, systemd is unable to determine the docked state. There is
no /sys/class/drm device (because of the fglrx driver) and systemd does
not find the input event source.
When
I applied the fix from the ppa yesterday, but the problem is still
present. This is on a Dell E6420, docked to an E-port Replicator Plus
with a pair of external monitors.
** Attachment added: grep -r . /sys/class/drm/* /tmp/monitors.txt
** Attachment added: xrandr --query /tmp/xrandr.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+attachment/4428458/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: journalctl -b /tmp/journal.txt
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+attachment/4428457/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have an HP zbook 15 G2 in the advanced dock and am having the same
problem of the system suspending on boot wit the lid closed. I tried the
PPA but the problem is still there. I've attached the output of the
commands you requested above that were taken after the PPA was applied.
cat
This was reworked recently in
https://github.com/systemd/systemd/commit/602a41c22a . That fix will
soon enter Wily (current development series), but for you I backported
it to 15.04 in https://launchpad.net/~pitti/+archive/ubuntu/sru-test .
Could you please enable that PPA, upgrade, and check if
Also seeing this issue when simply closing laptop lid (Razer Blade
2015). Clicking Suspend does not trigger this bug. It does NOT trigger
if I click Suspend, close lid, re-open lid. It only seems to trigger
when physically closing the lid while the machine is on.
--
You received this bug
** Changed in: systemd (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450009
Title:
suspends on closed lid, does not recognized external monitors/dock
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450009
Title:
Background: logind has some failsafe logic to go to suspend after 30 s
if the lid is closed and there are no external monitors connected
(http://cgit.freedesktop.org/systemd/systemd/commit/?id=ed4ba7e4f65215).
This would lead to effects like this if the lid switch is broken and
always says closed
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450009
Title:
suspends on closed lid, does not recognized external monitors/dock
To
I have a similar problem: When having my notebook (Lenovo T430) in the
dock, the external monitor is recognized, I see the login screen, but as
soon as I log in, the notebook goes to sleep.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Upon waking the login screen from forced sleep the system goes to sleep again
and again and again after 20-30sec upon leaving the system on login screen.
I thought upstart was a cure but am not so sure anymore because it started
happening there too.
$ cat /tmp/monitors.txt
15 matches
Mail list logo
