GNU bug report logs -
#48974
A possible shepherd bug (it's very minor)
Previous Next
Reported by: Joshua Branson <jbranso <at> dismail.de>
Date: Sat, 12 Jun 2021 13:27:02 UTC
Severity: normal
Done: Joshua Branson <jbranso <at> dismail.de>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
June 12, 2021 5:13 PM, "Leo Prikler" <leo.prikler <at> student.tugraz.at> wrote:
> Hi,
>
> Am Samstag, den 12.06.2021, 20:09 +0000 schrieb jbranso <at> dismail.de:
>
>> June 12, 2021 3:39 PM, "Leo Prikler" <leo.prikler <at> student.tugraz.at>
>> wrote:
>>
>> Am Samstag, den 12.06.2021, 09:26 -0400 schrieb Joshua Branson:
>>
>
> I'm pretty sure that the actual bug also exists, just not sure whether
> that's on your config or on shepherd. Using TTY1 for graphical stuff
> is also somewhat rare in Guix land, I presume. (Or rather, I can't
> think of it as anything but a container for debug output spam :D)
So...whay tty should I auto login to start my sway session? tty2? tty3?
>
> As for getting this to work only on TTY1, you do get the config object,
> so you can do stuff like
> (if (is-tty1? config) (inherit+autologin config) config)
> Note of course, that is-tty1? is not a procedure that's ready-made, but
> one that you'd need to build from primitives such as record accessors.
Thanks!
>
> Regards,
> Leo
This bug report was last modified 3 years and 318 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.