From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: help-guix@gnu.org
Subject: Re: xscreensaver on GuixSD
Date: Fri, 30 Jun 2017 14:47:47 +0200 [thread overview]
Message-ID: <87wp7tmyks.fsf@gnu.org> (raw)
In-Reply-To: <20170630.103902.1323821482778973177.post@thomasdanckaert.be> (Thomas Danckaert's message of "Fri, 30 Jun 2017 10:39:02 +0200 (CEST)")
Thomas Danckaert <post@thomasdanckaert.be> skribis:
> From: ludo@gnu.org (Ludovic Courtès)
> Subject: Re: xscreensaver on GuixSD
> Date: Thu, 29 Jun 2017 16:45:14 +0200
>
>> Thomas Danckaert <post@thomasdanckaert.be> skribis:
>>
>>> 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!
>>
>> I would start it from ~/.xsession, but perhaps there are fancier
>> ways to
>> do that.
>
> Strangely, after creating a ~/.xsession file, I wasn't able to log in
> to my gnome session anymore (though I didn't investigate this further
> and just deleted ~/.xsession again).
Maybe you forgot “chmod +x ~/.xsession”?
> What did work was to create a .desktop file in ~/.config/autostart.
> I've attached it here for future reference ;-)
>
> [Desktop Entry]
> Name=Screensaver
> Type=Application
> Exec=xscreensaver -nosplash
Interesting, I wonder what piece of software reads this file. Maybe
xfce-session and gnome-session?
Thanks for the tip,
Ludo’.
next prev parent reply other threads:[~2017-06-30 12:47 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 [this message]
2017-07-01 15:39 ` Thomas Danckaert
2017-07-06 3:40 ` Chris Marusich
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=87wp7tmyks.fsf@gnu.org \
--to=ludo@gnu.org \
--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).