From: notthewave <notthewave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] zzz sometimes causes frozen desktop after wakeup
Date: Thu, 11 Nov 2021 14:05:43 +0100 [thread overview]
Message-ID: <20211111130543.ZXiD8-EORJGC3a3S-7lbue90o1dZoW9drqcpcjyDlHw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33813@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Closed issue by notthewave on void-packages repository
https://github.com/void-linux/void-packages/issues/33813
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.13.19_1 x86_64-musl GenuineIntel uptodate rDFFFFFFFFFFFF*
* package:
*affected package(s) including the version*: ``pm-utils-1.4.1_8``
### Expected behavior
does not freeze after wakeup
### Actual behavior
sometimes freezes after wakeup
### Steps to reproduce the behavior
1. run zzz and wait for a few minutes
### Aditional Info
probably does not happen to everyone, so I suppose this is caused by something else I have installed.
here are my running services:
```
NetworkManager agetty-tty2 agetty-tty5 bluetoothd dbus mdnsd seatd ufw
acpid agetty-tty3 agetty-tty6 cups-browsed dcron nginx tlp virtlockd
agetty-tty1 agetty-tty4 avahi-daemon cupsd libvirtd ntpd udevd virtlogd
```
**tested with tty:**
recognizes keyboard input but can't stop zzz (CTRL+C)
next prev parent reply other threads:[~2021-11-11 13:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 14:28 [ISSUE] " notthewave
2021-10-31 12:48 ` Animeshz
2021-10-31 15:42 ` notthewave
2021-11-02 10:00 ` Animeshz
2021-11-02 10:04 ` Animeshz
2021-11-10 10:45 ` foopub
2021-11-10 21:08 ` notthewave
2021-11-10 21:09 ` notthewave
2021-11-10 21:18 ` notthewave
2021-11-10 22:13 ` notthewave
2021-11-10 23:54 ` notthewave
2021-11-10 23:55 ` notthewave
2021-11-10 23:56 ` notthewave
2021-11-10 23:57 ` notthewave
2021-11-11 0:13 ` notthewave
2021-11-11 0:14 ` notthewave
2021-11-11 11:40 ` notthewave
2021-11-11 13:04 ` notthewave
2021-11-11 13:05 ` notthewave
2021-11-11 13:05 ` notthewave [this message]
2021-11-11 16:49 ` notthewave
2021-11-11 16:49 ` [ISSUE] [CLOSED] " notthewave
2021-11-11 17:52 ` Animeshz
2021-11-11 17:53 ` Animeshz
2021-11-11 18:49 ` notthewave
2021-11-11 18:50 ` notthewave
2021-11-11 18:51 ` notthewave
2021-11-11 18:52 ` notthewave
2021-11-11 18:53 ` notthewave
2021-11-12 13:38 ` notthewave
2021-11-18 5:44 ` Animeshz
2021-11-18 5:52 ` Animeshz
2021-11-18 5:52 ` Animeshz
2021-11-25 12:35 ` leahneukirchen
2021-11-25 12:35 ` [ISSUE] [CLOSED] " leahneukirchen
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=20211111130543.ZXiD8-EORJGC3a3S-7lbue90o1dZoW9drqcpcjyDlHw@z \
--to=notthewave@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).