Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62620 - [alacritty] crashes on execution

Attached to Project: Community Packages
Opened by revel (revel) - Monday, 13 May 2019, 04:57 GMT
Last edited by Jiachen Yang (farseerfc) - Tuesday, 26 November 2019, 07:25 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Rebischke (Shibumi)
Jiachen Yang (farseerfc)
Architecture x86_64
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The new 0.3.2-x alacritty packages both crash for me just after start-up.
For the last few weeks I've been using the older 0.2.9-x version of this package, which worked just fine (still does).
But now, finally, I decided to investigate a bit.
At first, I cloned the github repository, built and tried it out - worked without problems.
Then, I built the arch package myself - the binary from the package crashed.
Then I removed all the patches - and it worked!
Finally, I narrowed the problem to be somewhere in the 'fix-transparency' patch - if enabled - the binary crashes for me.
I suspect the problem might be related to the nvidia-340xx drivers I'm using on this already quite old laptop.
Because of this, I don't really expect that it will be successfully resolved/fixed.
Just letting you know, since more people might be affected by this.

Additional info:
* alacritty 0.3.2-x
* nvidia-340xx drivers
This task depends upon

Closed by  Jiachen Yang (farseerfc)
Tuesday, 26 November 2019, 07:25 GMT
Reason for closing:  Fixed
Additional comments about closing:  The EventLoopV2 is merged to the upstream and 0.4.0 is released, that fixed the problem with transparency. fix-transparency patch is no longer applied, thus fixed this issue.
Comment by Antonio Rojas (arojas) - Monday, 13 May 2019, 06:22 GMT
Please post a backtrace of the crash
Comment by Jiachen Yang (farseerfc) - Monday, 13 May 2019, 07:32 GMT
The "fix-transparency.patch" was applied to solve an upstream regression: https://github.com/jwilm/alacritty/issues/2254 .
With this patch, transparency is fixed for intel/amd gpus, but causing problem for nvidia driver.
Please report your findings to the issue page to help upstream developer diagnosing this problem, with your specific driver and compositor being used, and do mention that we reverted the glutin branch using "fix-transparency.patch"
Comment by revel (revel) - Monday, 13 May 2019, 17:27 GMT
@arojas backtrace attached
@farseerfc will do
Many thanks to both of you for your attention!
   alacritty.log (2.7 KiB)
Comment by Christian Rebischke (Shibumi) - Sunday, 08 September 2019, 22:40 GMT
Hi,
does alacritty still crash after startup?
Comment by revel (revel) - Monday, 09 September 2019, 22:34 GMT
Yes it does, at least for me. But the 'solution' mentioned before still works, so it is good enough for me.
Comment by revel (revel) - Saturday, 05 October 2019, 01:31 GMT
I got a notification from upstream, that alacritty master just merged the glutin eventloop 2.0 patch, which supposedly makes this problematic 'fix-transparency' patch obsolete. There is no new release yet, but apparently this bug report here is going to be fixed soon.

https://github.com/jwilm/alacritty/pull/2438

Loading...