alacritty segmentation fault

  • Done
  • quality assurance status badge
Details
4 participants
  • Efraim Flashner
  • Liliana Marie Prikler
  • Sharlatan Hellseher
  • Steven Roose
Owner
unassigned
Submitted by
Steven Roose
Severity
normal
S
S
Steven Roose wrote on 4 Jan 16:32 +0100
(address . bug-guix@gnu.org)
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.
E
E
Efraim Flashner wrote on 5 Jan 13:52 +0100
(name . Steven Roose)(address . steven@roose.io)(address . 68243@debbugs.gnu.org)
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
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmWX+6sACgkQQarn3Mo9
g1F7qQ/8CMLBlNPyO+cqefLIpDGHc4QH5wcHpv8yOO/02gkiCOllpjicRcLwjT19
Q6xTAgcicwgYUd6f+GtLB8Z8G8wUunnl1Xfr1QSM21e0fS+7BwMc2ryP9v59Ljgh
7OsuKS/tEMUDjfDSRytmby/DFEVcMBphbtQk9/uIMOUjbvlQ4CkafYSLclNfYSLj
9MaeheR1BVL+tP7Bg5MeKQ4vxKlqMhSDNQYNoI3qqLc3uQUvxtMexipKfLaKF+3q
7T7SJhCVS7ozNA0zfp6pnuN8hkd5jCfzQCM10iqc0Bjgz/9BmWAU/6xD+Od57Bup
56Eqr+lFeGMn0Su2xMCgYbeSu3O9/BcF+2myFQTerCrC8Cz7paHDit8eAfO1a/qp
c4MJmUXEpRbuwDUPjulk4/cbMoCQMyG8l2S8zl2bxAkHMNqitc9x9feAB4T3b6l1
84XpabN8HPmlJ1lADdQLw8m/glW5kAf+XSkJSqAif4wE+hCGckdJr+P9RoYy8Xbe
LKIeCyy5h3Wt9XyeLNHRFDAHH/ClRI3BC3FUUFtk/KEBZzVL8FCjDK9TX8Izpdvj
ePbHIJK0Zz1gxlbOqQ0gfQjdfwMKifk2IB8DETQWraIjC8eFmL1SwjsU524VTx2k
G6GMu4WejuiHzKUGVegYS+833Mnpjr9ef7haLrJUjCI/ZYxolMw=
=0Ot3
-----END PGP SIGNATURE-----


E
E
Efraim Flashner wrote on 7 Jan 10:06 +0100
(address . steven@roose.io)(address . 68243@debbugs.gnu.org)
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
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmWaaZ0ACgkQQarn3Mo9
g1G/kg/5Af1o/EtE5fxuD3qFlOYuMLQwSshdQrJCj5mvhTjA/Uno/NJ5uApiQqSX
Bu//4S749UqdE95GVZgUNhvX913yywHNOijHmnaJmMJ843opC3gSosRUexsxPvGG
zIxl1I0cXre6VodJsw4hnu4VBka+z5QQDrtCtZXYaKVCywGdoyQZz5DI/1nM2bve
lpR17m2KhzEfdltnXY680MnO3wWZIzTz9MVWbpqzE3KnDyoFZL4ONX/s7EWyMKGK
lelTdcIyyr/6TbmXjvlwUIHWiVxplewz8ERbp84kCmkPjB5FUlRXQuWybP9RL8Ow
V1sIdNi/KfiystzHnjUcKi+/P3DBsgSBF0NVP+WJqcv+QkLK29iAZqw+seFvl5b6
mbOhlChecKCGyljTi70yLnGiwrA3DHpTJjHZflyQzhjFhCORo/uO40gKYzHripEn
/UFvPqdy4U6ejJ4wZ2F0pqU5zn6Hx6GFa1L9vyWriWx+0qJp+7m2O8R1xcTxOb5z
lD+fttfukaOMCTDj7clDd9J/VVuh9MMQKyI4jyo/EHOxDSyKlXS/qoJYSDAEFL8o
brCkzRTB6dNZIY8M+KvNaITWsclrewDGg4c0AihEN7gkZGZ07/0xyLms7+4Bmv+O
u5vI0ERkuLCTeFPlW5FrsS/yupEAqDJnsdt8tivDvFYWFuQ5E4g=
=0sO6
-----END PGP SIGNATURE-----


L
L
Liliana Marie Prikler wrote on 7 Jan 18:46 +0100
Re: alacritty segmentation fault
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
S
S
Steven Roose wrote on 11 Jan 16:55 +0100
Re: bug#68243: alacritty segmentation fault
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.
>>>
>>>
S
S
Sharlatan Hellseher wrote on 29 Mar 21:33 +0100
alacritty segmentation fault
(address . 68243-done@debbugs.gnu.org)
87il14n5gh.fsf@gmail.com
Fixed with 423ca234cbd7b4902fd2a3fbc089a6fd57ed5583.

Closing as resolved.

--
Oleg
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmEeB3micIcJkGAhndtcnv/Ys0rUFAmYHJZ4ACgkQdtcnv/Ys
0rWAlg/+PWFj5yGVz2RtVMJHFKswGZNO+Xlpy9/gF0saq8QU/pwyffi1L/x3xquu
OUlUE6KthQhCbpLW+5U8S9NsiZ+qdXLW8jW8Sjiv6ufsBYOcmeq9DZEB8IJOav/p
2OarhCcgQf7DNgZ6nMStDOmDOwJUaE2GH+h6a4thPuknsy81EQtQ8CaJ6CMXqLhv
Qm32Ht3rH7uDsmXz6NwmzfmKC026LMLrZ6kASP06T24GNJ9oRhvJyqzxogRwoa2l
MoqaXW4G07Bim3O2sKUWkxx9rsCtKQVLoPMYTkG++ZPAgRlD6ZPPNTGVDx9DtpRB
flo/r7HO6h5yCaWMD7BSokeLUN10fTwA7zE7nTeW01/LGL7ot3oCwH3EHVKHpyHO
tz+oAbOU4BpiCOYncQ05UL4KJhd94WhqJvKLjSGzgD/AYKp2CfW6yXR/D2+nTaCa
Ijw6OTK4aKmE9Ud7GTVmRm5kg5AUNp6CEGKhVPUfOGiTKhQ52KsSvrbeCXQNseYg
KIPMz2LBrtqY/kN1Os44MEaiYMy6wsJAAEVwWj7h0nbDf5MCAccxEQES1yIQQyvC
dtlEEGAGV9HOGUAaWcJ7EHS6tJW/nLe9pDtzYLvj8NsEPZAydcY9UFwcYCpYcmxD
C7UrHaR042aa4Oh6oSSKLbmpGGF0lk5QnZNIb/c0JTKFoaxpI/8=
=jBFs
-----END PGP SIGNATURE-----

Closed
?