From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Xscreensaver is very slow
Date: Tue, 18 Jun 2019 07:49:56 -0700 [thread overview]
Message-ID: <20190618144956.be7sc226jk33clsd@matica.foolinux.mooo.com> (raw)
In-Reply-To: <20190618093613.GX18009@ca.inter.net>
On 2019-06-18 05:36, Philip Webb wrote:
> Recently, I updated to Xscreensaver 5.42 & now it's very slow :
> some savers aren't moving at all.
>
> Has anyone else experienced this ? Does anyone have a solution ?
Does CPU use seem to go way up when xscreensaver starts?
Is glxgears running as it should?
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
next prev parent reply other threads:[~2019-06-18 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 9:36 [gentoo-user] Xscreensaver is very slow Philip Webb
2019-06-18 14:49 ` Ian Zimmerman [this message]
2019-06-18 15:54 ` [gentoo-user] " Philip Webb
2019-06-18 16:05 ` Dale
2019-06-18 17:11 ` Ian Zimmerman
2019-06-18 17:22 ` Jack
2019-06-19 11:44 ` Philip Webb
2019-06-20 10:55 ` Philip Webb
2019-06-20 13:04 ` Mick
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=20190618144956.be7sc226jk33clsd@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--cc=gentoo-user@lists.gentoo.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