unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Steven Roose <steven@roose.io>
To: 68243@debbugs.gnu.org
Subject: bug#68243: alacritty segmentation fault
Date: Thu, 4 Jan 2024 15:32:55 +0000	[thread overview]
Message-ID: <c22d0270-a178-a859-2acf-94006d19a068@roose.io> (raw)

I've been using alacritty as my default terminal for about a year 
without much issues. I'm currently on v0.12.3 of alacritty and use it 
with i3 and Xorg. A month or two ago I noticed that upgrading GuixSD 
broke alacritty. Since it's my main terminal and I didn't have any other 
terminals installed, I was forced to rollback my system through GRUB 
because I couldn't literally not even open a terminal to investigate or 
roll-back by CLI. I was trying another system upgrade now and noticed 
the issue is still not fixed. When running alacritty from an 
already-open alacritty only shows me "segmentation fault". The working 
and broken version is both 0.12.3, so I think it might not be an 
alacritty issue but more a linking/build issue. I'm basically stuck on a 
months-old Guix until this is fixed.

If there is any way I can be of use by providing debug/log files of some 
kind, please let me know.





             reply	other threads:[~2024-01-04 15:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 15:32 Steven Roose [this message]
2024-01-05 12:52 ` bug#68243: alacritty segmentation fault Efraim Flashner
     [not found]   ` <13ec7660-d10f-8864-f041-ad5a6398eb96@roose.io>
2024-01-07  9:06     ` Efraim Flashner
2024-01-11 15:55       ` Steven Roose
2024-01-07 17:46 ` Liliana Marie Prikler
2024-03-29 20:33 ` Sharlatan Hellseher

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=c22d0270-a178-a859-2acf-94006d19a068@roose.io \
    --to=steven@roose.io \
    --cc=68243@debbugs.gnu.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).