unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: chris <chris@bumblehead.com>
To: "(" <paren@disroot.org>
Cc: 65769@debbugs.gnu.org
Subject: bug#65769: greetd-wlgreet-sway-session result is blinking cursor
Date: Fri, 8 Sep 2023 09:01:41 -0700	[thread overview]
Message-ID: <ZPtFZZ6EzApJx9-T@guix-xps> (raw)
In-Reply-To: <87cyysllhs.fsf@disroot.org>

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




  reply	other threads:[~2023-09-08 16:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  3:04 bug#65769: greetd-wlgreet-sway-session result is blinking cursor chris
2023-09-06  5:00 ` bug#65769: wlgreet-sway-session chris
2023-09-06  5:10 ` chris
2023-09-06  5:22   ` chris
2023-09-06 12:34     ` Josselin Poiret via Bug reports for GNU Guix
2023-09-06  5:32   ` chris
2023-09-06 15:57 ` bug#65769: no elogind chris
2023-09-08 14:46 ` bug#65769: greetd-wlgreet-sway-session result is blinking cursor paren--- via Bug reports for GNU Guix
2023-09-08 15:31   ` chris
2023-09-08 15:37     ` paren--- via Bug reports for GNU Guix
2023-09-08 16:01       ` chris [this message]
2023-09-08 16:08         ` paren--- via Bug reports for GNU Guix
2023-09-09 11:11         ` Josselin Poiret via Bug reports for GNU Guix
2024-10-31 20:56           ` David Arroyo
2024-11-01 10:03             ` chris
2024-11-01 10:25             ` chris
2023-10-20  9:01 ` bug#65769: Hugo Buddelmeijer
2023-10-20 10:02   ` bug#65769: bdju via Bug reports for GNU Guix
2023-10-20 12:14     ` bug#65769: Hugo Buddelmeijer
2023-10-20 13:49       ` bug#65769: Hugo Buddelmeijer

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=ZPtFZZ6EzApJx9-T@guix-xps \
    --to=chris@bumblehead.com \
    --cc=65769@debbugs.gnu.org \
    --cc=paren@disroot.org \
    /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).