Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] `loginctl suspend` doesn't work properly on rootless Xorg.
Date: Sun, 07 Aug 2022 04:14:10 +0200	[thread overview]
Message-ID: <20220807021410.sOYK2U2DRFvkatO0UFnI4bquIjyVRfl4l4eBqGqgMvY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36183@inbox.vuxu.org>

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

Closed issue by aintyourcat on void-packages repository

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

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:  
  Void 5.15.26_1 x86_64 AuthenticAMD notuptodate rFFF
* package:  
  xorg-server-21.1.3_3

### Expected behavior
Laptop goes to sleep immediately when `loginctl suspend` issued & wake up properly when triggered (e.g a key on the keyboard pressed).

### Actual behavior
Laptop still awake for about 30 seconds with a blank screen before goes to sleep, moreover it kills Xorg when woken up.

Services status: [global_services.txt](https://github.com/void-linux/void-packages/files/8280891/global_services.txt),  [user_services.txt](https://github.com/void-linux/void-packages/files/8280892/user_services.txt)
Xorg's log: [Xorg.0.log](https://github.com/void-linux/void-packages/files/8280895/Xorg.0.log)
xinitrc: [xinitrc.txt](https://github.com/void-linux/void-packages/files/8280910/xinitrc.txt)

Notes:
1. The laptop is not even goes to sleep when I'm using this xinitrc: https://github.com/aintyourcat/dotfiles/blob/8e17830e68d1a45e367bf0af14d18835b03321c1/x/.config/X11/xinitrc#L19 (The only difference with the previous one is on the specified line).
2. `loginctl suspend` works fine on xorg-server installed from the repo, which requires the "needs_root_rights" key set to "yes" in /etc/X11/Xwrapper.config, however when I accidentaly run the same command with the same Xwrapper.config on the manually compiled xorg-server (which makes it's running as root) the issue is persist.
3. Similar issue i found: https://libredd.it/r/voidlinux/comments/nndnja/xorg_with_elogind_support_breaks_suspend_to_ram/.
4. My current workaround is to not run `loginctl suspend` but `zzz` and config elogind to ignore ACPI events like explained in: https://docs.voidlinux.org/config/power-management.html#elogind 

### Steps to reproduce the behavior
1. Install xorg-server with the elogind build option enabled via `xbps-src`.
6. Verify it: `xbps-query -p build-options xorg-server`.
7. Make sure that:
   - The "needs_root_rights" key equals to "no" in /etc/X11/Xwrapper.config.
   - The dbus & elogind services is running.
8. Start Xorg, in my case via `startx`.
9. Make sure the user which Xorg is running as isn't root: `ps -o user $(pgrep Xorg)`.
10. Run `loginctl suspend`.

      parent reply	other threads:[~2022-08-07  2:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17  2:52 [ISSUE] " aintyourcat
2022-04-24  5:30 ` deepaknegilachu
2022-07-24  2:13 ` github-actions
2022-08-07  2:14 ` github-actions [this message]

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=20220807021410.sOYK2U2DRFvkatO0UFnI4bquIjyVRfl4l4eBqGqgMvY@z \
    --to=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).