all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: paren--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: chris <chris@bumblehead.com>
Cc: 65769@debbugs.gnu.org
Subject: bug#65769: greetd-wlgreet-sway-session result is blinking cursor
Date: Fri, 08 Sep 2023 17:08:31 +0100	[thread overview]
Message-ID: <878r9glk9d.fsf@disroot.org> (raw)
In-Reply-To: <ZPtFZZ6EzApJx9-T@guix-xps>

chris <chris@bumblehead.com> 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...

  -- (




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

Thread overview: 17+ 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
2023-09-08 16:08         ` paren--- via Bug reports for GNU Guix [this message]
2023-09-09 11:11         ` Josselin Poiret via Bug reports for GNU Guix
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878r9glk9d.fsf@disroot.org \
    --to=bug-guix@gnu.org \
    --cc=65769@debbugs.gnu.org \
    --cc=chris@bumblehead.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.