From: Andreas Enge <andreas@enge.fr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 22835@debbugs.gnu.org
Subject: bug#22835: Autologin
Date: Sun, 28 Feb 2016 11:53:22 +0100 [thread overview]
Message-ID: <20160228105322.GA4648@solar> (raw)
In-Reply-To: <87wpppcegh.fsf@elephly.net>
On Sun, Feb 28, 2016 at 11:32:46AM +0100, Ricardo Wurmus wrote:
> Andreas Enge <andreas@enge.fr> writes:
> > Looking at the code in gnu/services/xorg.scm, I find the following definition:
> > (define* (slim-service #:key (slim slim)
> > (allow-empty-passwords? #t) auto-login?
> > (default-user "")
> > (theme %default-slim-theme)
> > (theme-name %default-slim-theme-name)
> > (xauth xauth) (shepherd shepherd) (bash bash)
> > (auto-login-session #~(string-append #$windowmaker
> > "/bin/wmaker"))
> > (startx (xorg-start-command)))
> > It also is a bit surprising; since I had added only xfce to my packages,
> > I expected this to start. Or is this impossible to realise?
>
> I have a working auto-login configuration using “modify-services”:
Sorry, I forgot to describe what "does not work" in my opinion. With
auto-login? set to #f, I get the login screen with a selection of sessions.
By default, xfce and ratpoison, since these are the packages present in the
default configuration. I deleted ratpoison from my configuration, so I can
only log in to xfce after typing user and password.
Now when I set auto-login? to #t, it does not log into xfce, but launches
the command given in auto-login-session. So I end up with windowmaker, which
did not even appear in the package list (but probably gets pulled in auto-
matically somehow). So at the least, the parameter needs to be documented.
I easily modified it to launch startxfce4 of the xfce package instead, and
ended up in xfce. Maybe this could be made the default choice anyway to
be consistent with our example desktop configuration?
More logically would be to log into one of the sessions that is also
proposed when auto-login? is set to #f. But this looks more complex, even
more so when there are several options present (which ones to choose?),
so maybe just documenting the command would be enough.
Andreas
next prev parent reply other threads:[~2016-02-28 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 23:14 bug#22835: Autologin Andreas Enge
2016-02-28 10:32 ` Ricardo Wurmus
2016-02-28 10:53 ` Andreas Enge [this message]
2016-02-28 15:55 ` Ludovic Courtès
2019-02-19 22:23 ` bug#22835: Close Andreas Enge
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=20160228105322.GA4648@solar \
--to=andreas@enge.fr \
--cc=22835@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).