Description of problem: Alacritty does not start on a very minimal installation with just sway and alacritty installed on top of the "minimal" environmental group. Version-Release number of selected component (if applicable): alacritty-0.9.9-1.fc35.x86_64 How reproducible: always Steps to Reproduce: 1. Install Fedora Linux using the Everything-ISO and select "Minimal" as the environmental group 2. On the installed system run "sudo dnf in sway alacritty" 3. Start sway, try to run alacritty from dmenu or $mod+Return Actual results: Alacritty does not start Expected results: Alacritty starts Additional info: It seems that alacritty has a runtime dependency on libwayland-egl (at least when running in a pure Wayland environment), as installing it solves the problem.
Interesting. I can confirm that alacritty builds against wayland-client crate with the "dlopen" feature, which explains why RPM cannot autodetect and generate this dependency automatically. I'll fix this with the next update (either by building without the dlopen feature, or by adding the dependency explicitly). Good find!
(In reply to Fabio Valentini from comment #1) > Interesting. I can confirm that alacritty builds against wayland-client > crate with the "dlopen" feature, which explains why RPM cannot autodetect > and generate this dependency automatically. I'll fix this with the next > update (either by building without the dlopen feature, or by adding the > dependency explicitly). Good find! I think building without dlopen isn't a good idea. When build without it uses a wayland-client implementation in rust which might lead to problems with the new nvidia driver because synchronisation isn't properly implemented in rust.
FEDORA-2022-4b0825aee9 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4b0825aee9
FEDORA-2022-d084859c1e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d084859c1e
FEDORA-2022-4b0825aee9 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4b0825aee9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4b0825aee9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d084859c1e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d084859c1e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d084859c1e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d084859c1e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-4b0825aee9 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.