From: Chris Marusich <cmmarusich@gmail.com>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: help-guix@gnu.org
Subject: Re: xscreensaver on GuixSD
Date: Wed, 05 Jul 2017 20:40:51 -0700 [thread overview]
Message-ID: <87fueamdvg.fsf@gmail.com> (raw)
In-Reply-To: <20170628.184214.1062466562203980561.post@thomasdanckaert.be> (Thomas Danckaert's message of "Wed, 28 Jun 2017 18:42:14 +0200 (CEST)")
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Thomas Danckaert <post@thomasdanckaert.be> writes:
> using GuixSD, I've added xscreensaver to my system configuration, by
> adding the following to the list of services:
>
> (screen-locker-service xscreensaver)
>
> this is enough to use xscreensaver (set up pam & make xscreensaver
> setuid), except for the fact that I have to start the xscreensaver
> daemon manually after booting.
>
> I'd like the xscreensaver daemon to start automatically. Has anyone
> set this up on their system? Do I need to define a custom service for
> this? Suggestions welcome!
>
> Thomas
Is it not possible to set up a system-wide service for this? I've never
taken the time to learn how screensavers or lock screens are
implemented. I'm surprised that it requires one daemon per user (per
session?) to implement!
For the record, I haven't gotten the screen-saver/screen-locker working
in GuixSD. Maybe by following your cue, I'll now be able to...!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-07-06 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 16:42 xscreensaver on GuixSD Thomas Danckaert
2017-06-29 14:45 ` Ludovic Courtès
2017-06-29 15:05 ` Daniel Pimentel
2017-06-30 8:39 ` Thomas Danckaert
2017-06-30 12:47 ` Ludovic Courtès
2017-07-01 15:39 ` Thomas Danckaert
2017-07-06 3:40 ` Chris Marusich [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fueamdvg.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=post@thomasdanckaert.be \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).