I downgraded cairo to 1.16.0-9.fc33 and it had no effect, the bug remained.
Thanks,
~spot
On Thu, Dec 17, 2020 at 11:19 AM Kalev Lember <kalevlember(a)gmail.com> wrote:
On Thu, Dec 17, 2020 at 5:12 PM Tom Callaway <spotrh(a)gmail.com>
wrote:
> Okay, this one has me stumped. Any chromium package I build through
> rawhide refuses to render most of the strings.
>
> At first, I thought this was gcc 11, but then I noticed that the first
> build with this problem was built before GCC 11 landed in rawhide (the
> compiler was the same n-v-r as the one in Fedora 33). Next, I thought it
> must be due to a newer system component that Chromium uses dynamically, but
> I was able to disprove that by installing the Fedora 33 build (same
> version-release) into a Rawhide VM, and it works fine. Google Chrome also
> works fine in rawhide.
>
> It seems that this must be something that is contained within chromium,
> that when built in rawhide, builds broken.
>
> Here's a screenshot of what it looks like:
>
https://twitter.com/spotfoss/status/1338918235719299072/photo/1
>
> Note that some text strings are rendering (in the UI, in the "search
> box"), but most of them are not (the "HTML5Test" text below the icon,
all
> of the strings in the developer console).
>
Can you try downgrading cairo to the f33 version (1.16.0), just to rule
that out? We updated it to the 1.17.4 development version in rawhide and I
think we're the first distro to ship it, so it could possibly have issues.
--
Kalev
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org