Date: Wed, 08 May 2024 10:46:10 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 278852] x11-fonts/juliamono: xft issue with 0.055 update Message-ID: <bug-278852-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278852 Bug ID: 278852 Summary: x11-fonts/juliamono: xft issue with 0.055 update Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: bugzilla.freebsd@omnilan.de CC: trueos@norwegianrockcat.com Flags: maintainer-feedback?(trueos@norwegianrockcat.com) CC: trueos@norwegianrockcat.com Created attachment 250528 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D250528&action= =3Dedit pkg-message to hint about color glyph problems with xterm/urxvt Hi, with the latest update, most fonts of this package can't be used in xterm(1) and urxvt(1)=20 anymore, which was not a problem with version 0.054. Error: xterm: unable to open font "", trying "fixed".... X Error of failed request: BadLength (poly request too large or internal X= lib length error) Major opcode of failed request: 139 (RENDER) Minor opcode of failed request: 20 (RenderAddGlyphs) Serial number of failed request: 88 Current serial number in output stream: 897 According to similar problems with noto-ColorEmoji fonts, the reason appare= ntly is the upstream fix for https://github.com/cormullion/juliamono/issues/201 = in 0.055 (adding color glyph). None of the Qt5 and GTK3 based apps which I tested are affected (kate, gede= it)!=20 And the 'Latin' version still works in xterm(1) e.g., but the difference mi= ght be not that obvious to everybody. Maybe the the attached pkg-message helps people who update or browse fonts = for their xterm... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278852-7788>