Bug 894329
| Summary: | t530 power button not working | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Aleksandar Kostadinov <akostadi> | |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 18 | CC: | akostadi, extras-orphan, gansalmon, itamar, jonathan, jpokorny, kernel-maint, madhu.chinakonda, notting | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 966186 (view as bug list) | Environment: | ||
| Last Closed: | 2013-05-22 20:09:58 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 966186 | |||
|
Description
Aleksandar Kostadinov
2013-01-11 13:00:12 UTC
There's no indication which kernel you're having troubles with. Is this still happening with 3.8.x? Yes, it does In LXDE, I am used to get a "logout menu" when touching power button.
As this bug reports, this does not happen with this setup.
I've also tried installing and running acpid, acpi_listen shows nothing.
It probably doesn't matter but I am running legacy mode, not UEFI.
# lsmod | grep -e ibm -e think
thinkpad_acpi 79427 0
snd 79379 16 snd_hda_codec_realtek,snd_hwdep,snd_timer,
snd_hda_codec_hdmi,snd_pcm,snd_seq,
snd_hda_codec,snd_hda_intel,thinkpad_acpi,
snd_seq_device
rfkill 21736 6 cfg80211,thinkpad_acpi,bluetooth
kernel-3.8.5-201.fc18.x86_64
acpid-2.0.18-3.fc18.x86_64
No change after updating to the newest BIOS (2.53 from 2013-02-22). And also no change regardless being in dockstation (and trying either power-off button) or not. Neither showkey nor acpi_listen shows anything. Jan, could you try holding the power key down for a second or two? It is strange but *without* updating the bios it is working for me when I hold it down for awhile. Sorry, I missed the updates (via email) on this bug as they were sorted to the kernel subfolder, which I do not visit very often :) Holding power key down for a while means power off for me (instant one, IIRC). I'd like to see short press -> logout/shutdown menu as it should be, IMHO. Jan, I meant holding for a second or two at max. Notover 4 seconds that usually powers the machine down. Aleksandar, thanks! You made me realize that the problem is somewhere else.
Respective bug+fix against acpid to make it work with LXDE will follow.
There were three things that made me misunderstand the situation:
(1.) I am used to power button taking effect immediately after press,
not after holding it 1-2 sec.
(2.) I am used to LXDE offering logout menu (as in lxsession-logout)
upon power button press
(3.) I am used to longer press of power button doing "circuit level"
instant shutdown
Hence I though that longer press was causing instant shutdown (3.) while
in fact, it was doing orderly shutdown triggered by interception of ACPI
event utilized on systemd level (logind). But this was so fast (perhaps
also thanks to SSD) that it realistically looked like the instant one :)
While nothing can probably be done about (1.), I solved the (2.) point
for myself and am about to ask to propagate my change into power.sh script
in acpid (should be pretty neutral in other use cases) so that LXDE
works as expected almost [*] out-of-the-box.
[*] One has to edit one line in /etc/systemd/logind.conf to allow acpid
power off button fallback; I expect such change in defaults wouldn't
yield much support
re [comment 9]: see [bug 966186]. Aleksandar, can this bug be closed, then? Yes, I'm closing as NOTABUG because the button is actually detected by kernel, just manufacturer chose to require a second of holding it down to send a button press event. |