Bug#758110: base: suspend to ram key (Fn+F4) does not work anymore

[Cedric Roux]

Hi Debian,

I don't have the problem anymore.

Here is what I did to remove it:
- apt-get install sysvinit-core sysvinit sysvinit-utils
- reboot
- apt-get remove --purge --auto-remove systemd
- apt-get install acpid
- apt-get install acpi-support

I don't remember if I removed the acpi thing before or after
systemd popped up (unwillingly). I guess it's after (why
would I have done it before? why did I include that information
in my previous email?).

Anyway, now fn-f4 suspends the computer. Putting the screen
down does not suspend it anymore (did I ask you to suspend?
No I just asked you to turn the screen off, so just do that
thank you). Everything is back in order. Systemd is at its
place, with all due respect to people's hard work (but you
know, it's also good to realize what you're doing just sucksTM
and give up and do something saner).

Regards,
Cédric.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758110: base: suspend to ram key (Fn+F4) does not work anymore

[Cédric Roux]

Package: base
Severity: normal

Dear Maintainer,

I did an upgrade of Debian testing yesterday and since then the Fn+F4
key on the laptop (ACER timeline X 5820TZG) does not suspend to RAM anymore.

I removed (apt-get purge) acpid, acpi-supoprt, acpi-support-base.

I use fvwm, not gnome/kde, that I run with startx.

I tried a cold boot, I tried in a linux console (i.e. no X).

I see that the key press is visible in /dev/input/event0 (the keyboard).
I see with xev that it is reported as keysym XF86Sleep in the X world.

I tried to look on the internet but could not find something that
helps, thus this email.

The apt-get dist-upgrade of yesterday seems to have installed systemd
instead of what was there before. It might be related, but:
journalctl -u systemd-logind.service -b
reports:
Watching system buttons on /dev/input/event3 (Sleep Button)
So I don't think the problem is there.
I suspect the kernel, since /dev/input/event3 seems to be
silent (cat /dev/input/event3 shows nothing, whereas
cat /dev/input/event0 does).

Thanks for any hint. If you don't have enough information, I may
provide more.

Regards,
Cédric.

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org