emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#35575: closed (Some graphical programs borked with Guix on Arch)


From: GNU bug Tracking System
Subject: bug#35575: closed (Some graphical programs borked with Guix on Arch)
Date: Mon, 22 Feb 2021 08:33:02 +0000

Your message dated Mon, 22 Feb 2021 19:31:44 +1100
with message-id <18b8b71f-f464-ea9a-7274-5853c07e4bd7@brendan.scot>
and subject line Re: bug#35575: closing. bug has not reoccurred since
has caused the debbugs.gnu.org bug report #35575,
regarding Some graphical programs borked with Guix on Arch
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
35575: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35575
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Some graphical programs borked with Guix on Arch Date: Sun, 5 May 2019 17:58:13 +1000
With Guix on Arch, Running Guix's Godot and cool-retro-term programs
results in a completely garbled GUI. Godot ran with OpenGL ES2 instead
of ES3 looks a bit better except the fonts fail to render correctly.
Cool-retro-term complains about how using a variable width font may
cause display alignment issues, although I'm not sure that is related.
Perhaps it indicates it is a font issue? The Arch versions work just
fine. I haven't installed Guix System  on this machine yet so I'm not
sure if they would work that way.

I have seen this kind of graphical artefact before with  KDE when I've
suspended my machine and it's come back all broken.. It may be related
to the fact that I have an AMD Radeon Fury X graphics card. (I haven't
explicitly installed any proprietary drivers; I think AMDGPU is free).

Any one have any clues on how to debug such a thing?

https://brendan.scot/p/borked-godot.png




--- End Message ---
--- Begin Message --- Subject: Re: bug#35575: closing. bug has not reoccurred since Date: Mon, 22 Feb 2021 19:31:44 +1100
On 1/4/20 12:53 am, Marius Bakke wrote:
Is this still relevant?  I haven't heard reports about this in a long
time, nor experienced it (anymore) on my super-experimental systems that
switch LLVM and Mesa versions all the time.  So I think the issue might
have been fixed upstream?


Closing because the issue seems to have only occurred once  a long time ago and may have been fixed up stream.



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]