Github messages for voidlinux
 help / color / mirror / Atom feed
From: travankor <travankor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: gtkgreet-0.7
Date: Sat, 23 Jan 2021 01:59:35 +0100	[thread overview]
Message-ID: <20210123005935.PHaklzH_bHiCigmPuX7GSOZSNfFHPgwRFt87PKvBlJc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20873@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

New comment by travankor on void-packages repository

https://github.com/void-linux/void-packages/pull/20873#issuecomment-765796299

Comment:
@kkga TBH greetd doesn’t handle bad configurations very well. I haven’t run into this error where all TTY’s are taken, but I have seen errors where greetd hangs the system.

You should be able to login again by booting to single user mode and disabling the greetd service.

As for the specific configuration error, I’m not sure yet. Greetd switched the config file to `greetd.conf`, but the old path should still be supported. There’s an IRC channel `#kennylevinsen` where the main author can help, too.

  parent reply	other threads:[~2021-01-23  0:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11  9:40 [PR PATCH] New package: gtkgreet-0.5 travankor
2020-04-11 18:40 ` [PR PATCH] [Updated] [WIP] " travankor
2020-04-11 19:02 ` travankor
2020-04-13  0:37 ` [PR PATCH] [Updated] " travankor
2020-05-26  2:57 ` travankor
2020-05-26  7:19 ` [PR PATCH] [Updated] New package: gtkgreet-0.6 travankor
2020-05-26  7:43 ` travankor
2020-05-26  8:43 ` travankor
2020-07-24 18:40 ` ericonr
2020-12-02  3:49 ` travankor
2020-12-24  1:25 ` [PR PATCH] [Updated] " travankor
2021-01-22 10:32 ` [PR REVIEW] New package: gtkgreet-0.7 travankor
2021-01-22 10:32 ` travankor
2021-01-22 12:52 ` kkga
2021-01-23  0:20 ` travankor
2021-01-23  0:21 ` travankor
2021-01-23  0:22 ` travankor
2021-01-23  0:30 ` travankor
2021-01-23  0:31 ` travankor
2021-01-23  0:59 ` travankor [this message]
2021-01-23 11:03 ` travankor
2021-01-23 11:03 ` travankor
2021-01-25 13:23 ` [PR PATCH] [Updated] " travankor
2021-01-25 13:39 ` travankor
2021-01-25 13:43 ` travankor
2021-01-31 20:49 ` [PR REVIEW] " ericonr
2021-01-31 20:49 ` ericonr
2021-01-31 20:49 ` ericonr
2021-02-02 10:34 ` travankor
2021-03-14 15:45 ` st3r4g
2021-11-06 22:47 ` [PR PATCH] [Closed]: " abenson
2023-09-06 16:29 [PR PATCH] " cinerea0
2023-12-11  1:47 ` github-actions

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=20210123005935.PHaklzH_bHiCigmPuX7GSOZSNfFHPgwRFt87PKvBlJc@z \
    --to=travankor@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).