Github messages for voidlinux
 help / color / mirror / Atom feed
From: keshto <keshto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] acpid and elogind don't play well with suspend
Date: Thu, 09 Apr 2020 09:20:29 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20780@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

New issue by keshto on void-packages repository

https://github.com/void-linux/void-packages/issues/20780

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
`Void 5.6.2_1 x86_64 GenuineIntel uptodate rFF`
* package:  
  *affected package(s) including the version*
```
elogind  (243.4_2)  [elogind-243.4_2]
libelogind  (243.4_2)  [libelogind-243.4_2]
acpid  (2.0.32_1)  [acpid-2.0.32_1]
```

### Expected behavior
Opening the laptop lid resumes the system
### Actual behavior
It wakes, but then suspends again almost instantly
### Steps to reproduce the behavior
There is a conflict between acpid and elogind. In /etc/acpi/handler.sh if we comment out the `zzz` things work as expected.
```
...
    button/lid)
        case "$3" in
                close)
                        # suspend-to-ram
                        logger "LID closed, suspending..."
                        #zzz
                        ;;
                open)   logger "LID opened" ;;
                *) logger "ACPI action undefined (LID): $2";;
        esac
        ;;
    *)
...
```
It seems that elogind (guessing from dmesg messages) is suspending before `zzz` is called and then when the lid opens `zzz` gets executed resulting in the suspend.


             reply	other threads:[~2020-04-09  7:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09  7:20 keshto [this message]
2020-04-09  7:23 ` keshto
2020-04-09  7:26 ` xtraeme
2020-04-09 19:16 ` keshto
2020-04-09 22:01 ` keshto
2020-04-09 22:01 ` [ISSUE] [CLOSED] " keshto
2020-04-10  7:11 ` travankor
2020-04-22 17:32 ` ericonr
2020-04-22 21:36 ` keshto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20780@inbox.vuxu.org \
    --to=keshto@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).