bug#65769: greetd-wlgreet-sway-session result is blinking cursor
Hi chris, chris writes: > Josselin sent this message intended for the thread and I think they are okay > with re-pasting here, > >> Usually elogind is responsible (through a PAM module) for creating this >> runtime directory. If you're not using elogind, you'll need to create this >> directory yourself somehow. I don't really think this is a bug per-se, as >> running without elogind is advanced stuff and its consequences should be >> understood by the user. oops, sorry for not replying to all (the cardinal sin of email conversation). > I support any conclusion from Josselin and unmatched-paren and want to add > these observations, > * wlgreet *does require* the greeter lock file > * wlgreet *does not require* elogind/logind > * not-advanced users like me may want to use wlgreet without elogind I'd still like feedback from actual users of wlgreet, as I have not used it myself. I do believe the only way it could work is because something takes care of creating the runtime directory. Best, -- Josselin Poiret signature.asc Description: PGP signature
bug#65769: greetd-wlgreet-sway-session result is blinking cursor
chris writes: > I support any conclusion from Josselin and unmatched-paren and want to add > these observations, > * wlgreet *does require* the greeter lock file > * wlgreet *does not require* elogind/logind > * not-advanced users like me may want to use wlgreet without elogind I'm not using elogind, either; just seatd. And yet it works still... -- (
bug#65769: greetd-wlgreet-sway-session result is blinking cursor
Josselin sent this message intended for the thread and I think they are okay with re-pasting here, > Usually elogind is responsible (through a PAM module) for creating this > runtime directory. If you're not using elogind, you'll need to create this > directory yourself somehow. I don't really think this is a bug per-se, as > running without elogind is advanced stuff and its consequences should be > understood by the user. I support any conclusion from Josselin and unmatched-paren and want to add these observations, * wlgreet *does require* the greeter lock file * wlgreet *does not require* elogind/logind * not-advanced users like me may want to use wlgreet without elogind
bug#65769: greetd-wlgreet-sway-session result is blinking cursor
chris writes: >> The greeter works after creating /run/user/986/wayland-1.lock and changing >> the >> owner of /run/user/986 and /run/user/986/wayland-1.lock to "greeter". wut. I don't remember ever having to do anything like that... > My system config is here > > > https://raw.githubusercontent.com/iambumblehead/guix-home/main/guix.system.scm Thanks! Now I know it's not malconfiguration; your config is essentially the same as mine.
bug#65769: greetd-wlgreet-sway-session result is blinking cursor
On 9月08日 金, ( wrote: > I believe that may have been moi :) This is really odd. I seem to be > the only person who has ever managed to make it work (though there's a > bit of a reporting bias there in that people who do manage probably > won't bring it up...) > > It would be great if anyone trying to use it could possibly reply here > with a link, attachment, or copy of the config.scm they use (whether > it's working for them or not; both are useful.) > > I'll start: > > https://git.sr.ht/~unmatched-paren/conf/tree/root/item/system.scm > > -- ( Thanks for replying to my issue :) A "solution" is discussed earlier in the thread https://issues.guix.gnu.org/65769#4 > The greeter works after creating /run/user/986/wayland-1.lock and changing > the owner of /run/user/986 and /run/user/986/wayland-1.lock to "greeter". My system config is here https://raw.githubusercontent.com/iambumblehead/guix-home/main/guix.system.scm
bug#65769: greetd-wlgreet-sway-session result is blinking cursor
chris writes: > In irc, I messaged the user who created greetd-wlgreet-sway-session and it > seems > other users have encountered the blinking cursor and no one knows of a > solution. If possible, I would like help troubleshoot and resolve the issue. I believe that may have been moi :) This is really odd. I seem to be the only person who has ever managed to make it work (though there's a bit of a reporting bias there in that people who do manage probably won't bring it up...) It would be great if anyone trying to use it could possibly reply here with a link, attachment, or copy of the config.scm they use (whether it's working for them or not; both are useful.) I'll start: https://git.sr.ht/~unmatched-paren/conf/tree/root/item/system.scm -- (
bug#65769: greetd-wlgreet-sway-session result is blinking cursor
Hello and thank you in advance for reading me. When defining wlgreet-sway-session in my system config, the result is a blinking cursor. There is no login screen. To login or issue any command, it is necessary to switch to a different tty with something like Alt+fn+F2. In irc, I messaged the user who created greetd-wlgreet-sway-session and it seems other users have encountered the blinking cursor and no one knows of a solution. If possible, I would like help troubleshoot and resolve the issue. My config file is here, https://raw.githubusercontent.com/iambumblehead/guix-home/main/guix.system.scm ```bash $ sudo tail -5 /var/log/greetd-1.log 2023-09-05 18:59:22 error: check_children: greeter exited without creating a session 2023-09-05 18:59:23 error: check_children: greeter exited without creating a session 2023-09-05 18:59:24 error: check_children: greeter exited without creating a session 2023-09-05 18:59:25 error: check_children: greeter exited without creating a session 2023-09-05 18:59:27 error: check_children: greeter exited without creating a session ``` I've tried defining some XDG vars in /home/greeter/.profile and sometimes this causes error messages to appear above the blinking cursor, but no positive result. Please anyone feel free to give advice or suggest any things that I might try.
