snapcrafters / alacritty Goto Github PK

This project forked from tunix/alacritty-snap

A community-maintained package to easily install Alacritty on Linux

License: MIT License

Shell 100.00%

alacritty's Introduction

This is the snap for Alacritty. It is a community-maintained package to easily install Alacritty on Ubuntu, Fedora, Debian and other major Linux distributions. It is available in the Snap Store, Ubuntu Software, and a number of other applications.

"A cross-platform, GPU enhanced terminal emulator."

Install

snap install alacritty --classic

(Don't have snapd installed?)

Published for with 💝 by Snapcrafters

How to contribute to this snap

Thanks for your interest! Below you find instructions to help you contribute to this snap.

The general workflow is to submit pull requests that merges your changes into the candidate branch here on GitHub. Once the pull request has been merged, a GitHub action will automatically build the snap and publish it to the candidate channel in the Snap Store. Once the snap has been tested thoroughly, we promote it to the stable channel so all our users get it!

Initial setup

If this is your first time contributing to this snap, you first need to set up your own fork of this repository.

Fork the repository into your own GitHub namespace.
Clone your fork, so that you have it on your local computer.
Configure your local repo. To make things a bit more intuitive, we will rename your fork's remote to myfork, and add the snapcrafters repo as snapcrafters.
```
git remote rename origin myfork
git remote add snapcrafters https://github.com/snapcrafters/alacritty.git
git fetch --all
```

Submitting changes in a pull request

Once you're all setup for contributing, keep in mind that you want the git information to be all up-to-date. So if you haven't "fetched" all changes in a while, start with that:

git fetch --all -p

Now that your git metadata has been updated you are ready to create a bugfix branch, make your changes, and open a pull request.

All pull requests should go to the stable branch so create your branch as a copy of the stable branch:
```
git checkout -b my-bugfix-branch snapcrafters/candidate
```
Make your desired changes and build a snap locally for testing:
```
snapcraft --use-lxd
```
After you are happy with your changes, commit them and push them to your fork so they are available on GitHub:
```
git commit -a
git push -u myfork my-bugfix-branch
```
Then, open up a pull request from your my-bugfix-branch to the snapcrafters/candidate branch.
Once you've opened the pull request, it will automatically trigger the build-test action that will launch a build of the snap. You can watch the progress of the snap build from your pull request (Show all checks -> Details). Once the snap build has completed, you can find the built snap (to test with) under "Artifacts".
Someone from the team will review the open pull request and either merge it or start a discussion with you with additional changes or clarification needed.
Once the pull request has been merged into the stable branch, a GitHub action will rebuild the snap using your changes and publish it to the Snap Store into the candidate channel. After sufficient testing of the snap from the candidate channel, one of the maintainers or administrators will promote the snap to the stable branch in the Snap Store.

Maintainers

@tunix

License

The license the build files in this repository is MIT
Alacritty is licensed as Apache-2.0

alacritty's People

Contributors

Stargazers

Watchers

Forkers

kaihowl jayesh1910 daboross jssotomdz ce-shane spyridonas setharnold soumyadghosh developers81828182 compuguy jnsgruk sergiusens

alacritty's Issues

Call for testing `alacritty`

A new version (0.13.1) of alacritty was just pushed to the latest/candidate channel in the snap store. The following revisions are available.

CPU Architecture	Revision
amd64	115
arm64	119
armhf	118
ppc64el	117
s390x	116

Automated testing

If configured, the snap will be installed in a VM, and any test results or screenshots will be posted to this issue as a comment shortly.

How to test it manually

Stop the application if it was already running

Upgrade to this version by running

snap refresh alacritty --channel latest/candidate

Start the app and test it out.
Finally, add a comment below explaining whether this app is working, and include the output of the following command.
```
snap version; lscpu | grep Architecture; snap info alacritty | grep installed
```

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] latest/stable [done].

For example

To promote a single revision, run /promote <rev> latest/stable

To promote multiple revisions, run /promote <rev>,<rev> latest/stable

To promote a revision and close the issue, run /promote <rev>,<rev> latest/stable done

You can promote all revisions that were just built with:

/promote 115,119,118,117,116 latest/stable done

[BUG] Mouse cursor changes theme when over the alacritty window

Describe the bug

My mouse cursor changes to a weird default white one when over the Alacritty window. This does not happen with other snaps installed on the system like Firefox.

To Reproduce

Steps to reproduce the behavior:

Open the Alacritty snap on Ubuntu 24.04 default desktop
Move the mouse cursor over the Alacritty window
Observe that the cursor changes from the black with white outline default theme to an all white cursor with a different shape

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Screencast.from.2024-04-30.18-03-47.webm

Environment (please complete the following information):

OS: Ubuntu 24.04 LTS
Alacritty Version: 0.13.2
Graphics Cards: Intel integrated graphics

[BUG] Conflict of version for DRI driver

Describe the bug

When launching any application using mesa from alacritty, I get the following error message: DRI driver not from this Mesa build ('23.2.1-1ubuntu3.1~22.04.2' vs '24.0.5-1ubuntu1').

When I install alacritty through cargo install alacritty everything works as expected.

To Reproduce

Steps to reproduce the behavior:

Install alacritty from snap (snap install alacritty --classic)
Launch an alacritty terminal
Run glxinfo from this terminal
See error

Expected behavior

No error should occur.

Environment (please complete the following information):

OS: Ubuntu 24.04
Alacritty Version: 0.13.2
Graphics Cards: AMD Ryzen 7 7840U w/ Radeon 780M Graphics

Additional context

Shell output:

$ glxinfo
name of display: :0
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
using driver amdgpu for 4
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
pci id for fd 4: 1002:15bf, driver radeonsi
MESA-LOADER: dlopen(/snap/alacritty/125/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so)
DRI driver not from this Mesa build ('23.2.1-1ubuntu3.1~22.04.2' vs '24.0.5-1ubuntu1')
failed to load driver: radeonsi
using driver amdgpu for 4
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
pci id for fd 4: 1002:15bf, driver radeonsi
MESA-LOADER: dlopen(/snap/alacritty/125/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so)
DRI driver not from this Mesa build ('23.2.1-1ubuntu3.1~22.04.2' vs '24.0.5-1ubuntu1')
failed to load driver: radeonsi
MESA-LOADER: dlopen(/snap/alacritty/125/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so)
did not find extension DRI_Kopper version 1
DRI driver not from this Mesa build ('23.2.1-1ubuntu3.1~22.04.2' vs '24.0.5-1ubuntu1')
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  54
  Current serial number in output stream:  55

LIBGL_DEBUG output (only if you have graphics related issue):

$ LIBGL_DEBUG=verbose alacritty
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
libGL: using driver amdgpu for 21
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
libGL: pci id for fd 21: 1002:15bf, driver radeonsi
libGL: MESA-LOADER: dlopen(/snap/alacritty/125/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/username/.drirc: No such file or directory.
/usr/share/libdrm/amdgpu.ids version: 1.0.0
libGL: Using DRI3 for screen 0

[BUG] GLIBC_2.38 not found after last update.

Describe the bug

After last update, on Ubuntu 23.10, alacritty fails to launch with:

libGL error: MESA-LOADER: failed to open iris: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: swrast
Error: Error { raw_code: Some(167), raw_os_message: Some("GLXBadFBConfig"), kind: BadConfig }

To Reproduce

Steps to reproduce the behavior:

Open any other terminal
execute alacritty
Error output

Expected behavior

Alacritty launchs

Screenshots

N/A

Environment (please complete the following information):

OS: Ubuntu 23.10
Alacritty Version: latest/stable: 0.13.1 2024-02-27 (115) 95MB classic
Graphics Cards: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] and NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] (rev a1)

Additional context

$ alacritty -vvv

Created log file at "/tmp/Alacritty-20552.log"
[0.000001035s] [INFO ] [alacritty] Welcome to Alacritty
[0.000079476s] [INFO ] [alacritty] Version 0.13.1 (fe2a3c56)
[0.000092075s] [INFO ] [alacritty] Running on X11
[0.000505901s] [INFO ] [alacritty] Configuration files loaded from:
                                     "/home/samuel/.config/alacritty/alacritty.toml"
                                     "/home/samuel/.config/alacritty/themes/everforest.toml"
[0.007185353s] [INFO ] [alacritty] Using GLX 1.4
libGL error: MESA-LOADER: failed to open iris: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: swrast
[0.068869400s] [DEBUG] [alacritty] Picked GL Config:
                                     buffer_type: Some(Rgb { r_size: 8, g_size: 8, b_size: 8 })
                                     alpha_size: 8
                                     num_samples: 0
                                     hardware_accelerated: true
                                     supports_transparency: Some(true)
                                     config_api: Api(OPENGL | GLES1 | GLES2)
                                     srgb_capable: false
[0.074639805s] [INFO ] [alacritty] Window scale factor: 1
[0.082538591s] [INFO ] [alacritty] Goodbye
Deleted log file at "/tmp/Alacritty-20552.log"
Error: Error { raw_code: Some(167), raw_os_message: Some("GLXBadFBConfig"), kind: BadConfig }

LIBGL_DEBUG output (only if you have graphics related issue):

$ LIBGL_DEBUG=verbose alacritty
...
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/samuel/.drirc: No such file or directory.
libGL: using driver i915 for 17
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/samuel/.drirc: No such file or directory.
libGL: using driver i915 for 17
libGL: pci id for fd 17: 8086:3e9b, driver iris
libGL: MESA-LOADER: failed to open /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri/iris_dri.so: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2)
libGL error: MESA-LOADER: failed to open iris: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL: using driver i915 for 17
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/samuel/.drirc: No such file or directory.
libGL: using driver i915 for 17
libGL: pci id for fd 17: 8086:3e9b, driver iris
libGL: MESA-LOADER: failed to open /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri/iris_dri.so: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2)
libGL error: MESA-LOADER: failed to open iris: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL: MESA-LOADER: failed to open /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2)
libGL error: MESA-LOADER: failed to open swrast: /snap/core22/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libxml2.so.2) (search paths /snap/alacritty/115/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
libGL error: failed to load driver: swrast
Error: Error { raw_code: Some(167), raw_os_message: Some("GLXBadFBConfig"), kind: BadConfig }

Call for testing `alacritty`

A new version (0.13.1) of alacritty was just pushed to the latest/candidate channel in the snap store. The following revisions are available.

CPU Architecture	Revision
amd64	120
arm64	123
armhf	124
ppc64el	121
s390x	122

Automated testing

If configured, the snap will be installed in a VM, and any test results or screenshots will be posted to this issue as a comment shortly.

How to test it manually

Stop the application if it was already running

Upgrade to this version by running

snap refresh alacritty --channel latest/candidate

Start the app and test it out.
Finally, add a comment below explaining whether this app is working, and include the output of the following command.
```
snap version; lscpu | grep Architecture; snap info alacritty | grep installed
```

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] latest/stable [done].

For example

To promote a single revision, run /promote <rev> latest/stable

To promote multiple revisions, run /promote <rev>,<rev> latest/stable

To promote a revision and close the issue, run /promote <rev>,<rev> latest/stable done

You can promote all revisions that were just built with:

/promote 120,123,124,121,122 latest/stable done

[BUG] Awful Snap Bug Title Here

Describe the bug

If i install alacritty by snap, i have problems with pemissions

To Reproduce
sudo snap install alacritty --classic
Create config by path ~/.config/alacritty/alacritty.toml
try to install themes

Steps to reproduce the behavior:
add same config is ok, but if i want to use themes:
instal curv:
1 sudo snap install curl,
install themes
2 curl -LO --output-dir ~/.config/alacritty https://github.com/catppuccin/alacritty/raw/main/catppuccin-latte.toml
have error:
/home/myname/.config/alacritty/catppuccin-latte.toml: Permission
Warning: denied

Expected behavior

want to get no permission errors

Screenshots

If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

OS: [e.g. Ubuntu 20.04.3 LTS]
Alacritty Version:
Graphics Cards:

Additional context

Shell output:

$ alacritty -vvv
...

LIBGL_DEBUG output (only if you have graphics related issue):

$ LIBGL_DEBUG=verbose alacritty
...

LD_LIBRARY_PATH shouldn't be set

LD_LIBRARY_PATH is set to "$SNAP/usr/lib/$CRAFT_ARCH_TRIPLET:$SNAP/lib/$CRAFT_ARCH_TRIPLET".

This causes problems when running other things inside alacritty. For example, running leanc of the Lean programming language leads to symbol lookup errors of clang.

Is there anyway to avoid it?

Call for testing `alacritty`

A new version (0.13.2) of alacritty was just pushed to the latest/candidate channel in the snap store. The following revisions are available.

CPU Architecture	Revision
amd64	125
arm64	126
armhf	128
ppc64el	129
s390x	127

Automated testing

If configured, the snap will be installed in a VM, and any test results or screenshots will be posted to this issue as a comment shortly.

How to test it manually

Stop the application if it was already running

Upgrade to this version by running

snap refresh alacritty --channel latest/candidate

Start the app and test it out.
Finally, add a comment below explaining whether this app is working, and include the output of the following command.
```
snap version; lscpu | grep Architecture; snap info alacritty | grep installed
```

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] latest/stable [done].

For example

To promote a single revision, run /promote <rev> latest/stable

To promote multiple revisions, run /promote <rev>,<rev> latest/stable

To promote a revision and close the issue, run /promote <rev>,<rev> latest/stable done

You can promote all revisions that were just built with:

/promote 125,126,128,129,127 latest/stable done

Call for testing `alacritty`

A new version (0.13.1) of alacritty was just pushed to the latest/candidate channel in the snap store. The following revisions are available.

CPU Architecture	Revision
amd64	110
arm64	113
armhf	114
ppc64el	112
s390x	111

Automated testing

If configured, the snap will be installed in a VM, and any test results or screenshots will be posted to this issue as a comment shortly.

How to test it manually

Stop the application if it was already running

Upgrade to this version by running

snap refresh alacritty --channel latest/candidate

Start the app and test it out.
Finally, add a comment below explaining whether this app is working, and include the output of the following command.
```
snap version; lscpu | grep Architecture; snap info alacritty | grep installed
```

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] latest/stable [done].

For example

To promote a single revision, run /promote <rev> latest/stable

To promote multiple revisions, run /promote <rev>,<rev> latest/stable

To promote a revision and close the issue, run /promote <rev>,<rev> latest/stable done

You can promote all revisions that were just built with:

/promote 110,113,114,112,111 latest/stable done

snapcrafters / alacritty Goto Github PK

alacritty's Introduction

Install

How to contribute to this snap

Initial setup

Submitting changes in a pull request

Maintainers

License

alacritty's People

Contributors

Stargazers

Watchers

Forkers

alacritty's Issues

Automated testing

How to test it manually

How to release it

Automated testing

How to test it manually

How to release it

Automated testing

How to test it manually

How to release it

Automated testing

How to test it manually

How to release it

Recommend Projects

Recommend Topics

Recommend Org