From: Efraim Flashner <efraim@flashner.co.il>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: valentignatev@gmail.com, othacehe@gnu.org, fulbert@bluewin.ch,
mail@nicolasgoaziou.fr, 49639@debbugs.gnu.org
Subject: bug#49639: Alacritty doesn't start.
Date: Mon, 19 Jul 2021 15:08:25 +0300 [thread overview]
Message-ID: <YPVrOYFMnsDasWSp@3900XT> (raw)
In-Reply-To: <ae94bac6-ed5a-eb4f-4dc8-ee618a2acfce@raghavgururajan.name>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Mon, Jul 19, 2021 at 05:34:55AM -0400, Raghav Gururajan wrote:
> Hello Guix!
>
> Upon running `alacritty` in terminal, I get the following error:
>
> Xlib: sequence lost (0x1006f > 0x71) in reply type 0x0!
> Xlib: sequence lost (0x10074 > 0x76) in reply type 0x0!
> Xlib: sequence lost (0x10079 > 0x7b) in reply type 0x0!
> Xlib: sequence lost (0x1007e > 0x80) in reply type 0x0!
> Xlib: sequence lost (0x10083 > 0x85) in reply type 0x0!
> Created log file at "/tmp/Alacritty-27896.log"
> [2021-07-19 05:26:41.842621210] [ERROR] [alacritty] Alacritty encountered an
> unrecoverable error:
>
> There was an error
> initializing the shaders: Failed compiling shader: 0:1(10): error: GLSL 3.30
> is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES
>
What GPU do you have? It's likely that if it's old enough it doesn't
support the GPU features that alacritty uses. It used to happen to me
with my old laptop.
--
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-07-19 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 9:34 bug#49639: Alacritty doesn't start Raghav Gururajan via Bug reports for GNU Guix
2021-07-19 12:08 ` Efraim Flashner [this message]
[not found] ` <CADXmXkieSPFg1DPTsVq4-aK7zvjtm-ZfjRT83BTs2JoyVxhkgQ@mail.gmail.com>
2021-07-21 16:56 ` Raghav Gururajan via Bug reports for GNU Guix
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=YPVrOYFMnsDasWSp@3900XT \
--to=efraim@flashner.co.il \
--cc=49639@debbugs.gnu.org \
--cc=fulbert@bluewin.ch \
--cc=mail@nicolasgoaziou.fr \
--cc=othacehe@gnu.org \
--cc=rg@raghavgururajan.name \
--cc=valentignatev@gmail.com \
/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).