alacritty segmentation fault

Done

Details

4 participants

Efraim Flashner
Liliana Marie Prikler
Sharlatan Hellseher
Steven Roose

Owner: unassigned

Submitted by: Steven Roose

Severity: normal

Steven Roose wrote on 4 Jan 16:32 +0100

Recipients:(address . bug-guix@gnu.org)

Message-ID:c22d0270-a178-a859-2acf-94006d19a068@roose.io

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.

Efraim Flashner wrote on 5 Jan 13:52 +0100

Recipients:(name . Steven Roose)(address . steven@roose.io)(address . 68243@debbugs.gnu.org)

Message-ID:ZZf7q0DvOinQmTOP@3900XT

On Thu, Jan 04, 2024 at 03:32:55PM +0000, Steven Roose wrote:

Toggle quote (15 lines)> 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.

Looking at 'alacritty --help' it looks like you can try adding -v (up to
3) to get a more verbose output so hopefully we get more of an error
message.

Which generation are you on that is working for you? Which one do you
know is segfaulting? I'd like to try to narrow it down.

-- 
Efraim Flashner   <efraim@flashner.co.il>   ????? ?????
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Efraim Flashner wrote on 7 Jan 10:06 +0100

Recipients:(address . steven@roose.io)(address . 68243@debbugs.gnu.org)

Message-ID:ZZppoD7tMsHxJa9Z@3900XT

I meant more of what's the guix version from the generation which

contains the non-working alacritty.

On Fri, Jan 05, 2024 at 02:51:34PM +0000, steven@roose.io wrote:

Toggle quote (32 lines)> How can I check generations for packages? `guix package -l` doesn't seem to show any useful information.
> 
> I can't seem to find out what the syntax should be for the PATTERN arguments in guix package, like `guix package --list-generations=PATTERN`.
> 
> I try `guix package -l alacritty`, `guix package --list-generations=alacritty` but always get `invalid syntax: alacritty`..
> 
> On 1/5/24 12:52 PM, Efraim Flashner <efraim@flashner.co.il> wrote:
> > On Thu, Jan 04, 2024 at 03:32:55PM +0000, Steven Roose wrote:
> > > 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.
> > 
> > Looking at 'alacritty --help' it looks like you can try adding -v (up to
> > 3) to get a more verbose output so hopefully we get more of an error
> > message.
> > 
> > Which generation are you on that is working for you? Which one do you
> > know is segfaulting? I'd like to try to narrow it down.
> > 
> > 

-- 
Efraim Flashner   <efraim@flashner.co.il>   ????? ?????
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Liliana Marie Prikler wrote on 7 Jan 18:46 +0100

Re: alacritty segmentation fault

Recipients:

Message-ID:601f2dfa2a36cec8198897b27e5877c1c6da43e9.camel@gmail.com

Am Donnerstag, dem 04.01.2024 um 15:32 +0000 schrieb Steven Roose:

Toggle quote (15 lines)> 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.

I suppose this might be related to the mesa update we had some while
ago.  I myself noticed that GNOME 4 apps stopped working due to some
very, very weird behaviour of the driver that I still don't comprehend.
Anyway, switching to the cairo renderer per environment variable worked
for me.  Perhaps there's something similar you can do for alacritty (or
otherwise switch back to the older mesa with an inferior/use any other
VTE for the time being).

Cheers

Steven Roose wrote on 11 Jan 16:55 +0100

Re: bug#68243: alacritty segmentation fault

Recipients:

Message-ID:b94f7220-4bd1-54e5-5c2e-76ac4f813fcf@roose.io

This is what guix system describe shows:

> commit: aabfddbe8bc16fa82067e88e7d79c8c1bc802414

So that should be the one that works, I guess. The newer one doesn't.

On 1/7/24 09:06, Efraim Flashner wrote:

Toggle quote (34 lines)> I meant more of what's the guix version from the generation which
> contains the non-working alacritty.
>
> On Fri, Jan 05, 2024 at 02:51:34PM +0000, steven@roose.io wrote:
>> How can I check generations for packages? `guix package -l` doesn't seem to show any useful information.
>>
>> I can't seem to find out what the syntax should be for the PATTERN arguments in guix package, like `guix package --list-generations=PATTERN`.
>>
>> I try `guix package -l alacritty`, `guix package --list-generations=alacritty` but always get `invalid syntax: alacritty`..
>>
>> On 1/5/24 12:52 PM, Efraim Flashner <efraim@flashner.co.il> wrote:
>>> On Thu, Jan 04, 2024 at 03:32:55PM +0000, Steven Roose wrote:
>>>> 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.
>>> Looking at 'alacritty --help' it looks like you can try adding -v (up to
>>> 3) to get a more verbose output so hopefully we get more of an error
>>> message.
>>>
>>> Which generation are you on that is working for you? Which one do you
>>> know is segfaulting? I'd like to try to narrow it down.
>>>
>>>

Sharlatan Hellseher wrote on 29 Mar 21:33 +0100

alacritty segmentation fault

Recipients:(address . 68243-done@debbugs.gnu.org)

Message-ID:87il14n5gh.fsf@gmail.com

Fixed with 423ca234cbd7b4902fd2a3fbc089a6fd57ed5583.

Closing as resolved.

Oleg

Closed

Your comment

This issue is archived.

To comment on this conversation send an email to 68243@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it

mumi current 68243

Then, you may apply the latest patchset in this issue (with sign off)

mumi am -- -s

Or, compose a reply to this issue

mumi compose

Or, send patches to this issue

mumi send-email *.patch

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date