From: chris <chris@bumblehead.com>
To: David Arroyo <david@aqwari.net>
Cc: "\(" <paren@disroot.org>, Josselin Poiret <dev@jpoiret.xyz>,
65769@debbugs.gnu.org
Subject: bug#65769: greetd-wlgreet-sway-session result is blinking cursor
Date: Fri, 1 Nov 2024 03:25:50 -0700 [thread overview]
Message-ID: <wvfmmepef37eqjigz2mftsxsz5yj2qmmo67ixucz2mka7y2izs@ugwsu2wspppu> (raw)
In-Reply-To: <d4962d15-d4a4-49d3-8a27-d5e8c5b2183b@app.fastmail.com>
A week or two ago, wlgreet-sway-session started booting a blinking cursor again. I used ssh to get in, disable it and reconfigure and never took another look. Just now, per your advice, added "users" to `greeter-supplementary-groups`, reconfigured and rebooted and it works again!
--
好きなものを、好きなもので、好きなように作る。
next prev parent reply other threads:[~2024-11-01 10:39 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
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 [this message]
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=wvfmmepef37eqjigz2mftsxsz5yj2qmmo67ixucz2mka7y2izs@ugwsu2wspppu \
--to=chris@bumblehead.com \
--cc=65769@debbugs.gnu.org \
--cc=david@aqwari.net \
--cc=dev@jpoiret.xyz \
--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.