Bug 229684 - x11/alacritty: Won't start since update
Summary: x11/alacritty: Won't start since update
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Niclas Zeising
URL:
Keywords:
Depends on: 229857
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-11 03:35 UTC by Greg Fitzgerald
Modified: 2018-10-12 14:03 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (zeising)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Fitzgerald 2018-07-11 03:35:35 UTC
I recently updated my packages, after updating from g20180126_1 to g20180126_3 alacritty no longer starts. I get the following error.

Error creating GL context; Couldn't find any pixel format that matches the criterias.

I'm on FreeBSD-11.2-RELEASE with the amdgpu drivers from drm-kmod-next.
Comment 1 Walter Schwarzenfeld 2018-07-11 04:18:18 UTC
I cannot test it, cause alacritty starts without problems on my system, but maybe this can solve this:

https://github.com/lo48576/alacritty/commit/b274a9f5055115b152159c0f146542a91fb4bb63
Comment 2 Greg Fitzgerald 2018-07-11 04:26:14 UTC
I'm not sure if that patch works yet or not, I'll try to test it tomorrow. That being said I just installed git using cargo and it works fine from git.
Comment 3 Niclas Zeising freebsd_committer freebsd_triage 2018-07-18 11:08:17 UTC
I thought this issue was resolved already.

There's a PR for an updated version, perhaps that solves this issue as well?
See PR 229857
Comment 4 Greg Fitzgerald 2018-07-18 11:16:09 UTC
Sorry, I forgot to come back and update this issue. That patch did fix the issue for me.
Comment 5 Tobias Kortkamp freebsd_committer freebsd_triage 2018-10-12 14:03:11 UTC
Closing as fixed per comment #3 and comment #4.