Github messages for voidlinux
 help / color / mirror / Atom feed
From: z411 <z411@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Attempting to suspend on Wayland+KDE+nVidia breaks system completely
Date: Wed, 20 Sep 2023 20:52:19 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46161@inbox.vuxu.org> (raw)

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

New issue by z411 on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

Void 6.3.13_1 x86_64 AuthenticAMD uptodate rrrrmmnFFFFF

### Package(s) Affected

kwin-5.27.7_1, nvidia-535.104.05_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

When clicking sleep the system should suspend.

### Actual behaviour

When clicking sleep nothing happens, the screen just gets locked.
Instead, the system keeps working but it starts behaving strangely:

1. Firefox stops being able to open new pages or tabs; it seems that the backend of the browser hangs completely.
2. Screen starts freezing randomly for ~15 seconds then unfreezing
3. KDE System settings doesn't start
4. Nothing happens when attempting to change TTY with CTRL+Fn keys
5. Attempting to log out through the GUI freezes the plasma shell
6. Attempting to log out by killing all user processes (`pkill -9 -U 1000`) freezes the system
7. Attempting to reboot with the `reboot` command actually suspends the system (!)

This works normally in Debian+Wayland (I think it has some nvidia-suspend systemd services that might be required?).
It also works normally in Void+Xorg.

### Steps to reproduce

1. Open KDE system menu
2. Click "Sleep"
3. Observe the system start behaving strangely instead of going to sleep

             reply	other threads:[~2023-09-20 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 18:52 z411 [this message]
2023-11-08 20:49 ` CuriousApe2020
2023-11-10  5:40 ` z411
2023-11-20 15:12 ` m3tav3rse
2023-12-05 13:25 ` z411

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-46161@inbox.vuxu.org \
    --to=z411@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).