-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
X_OpenFont BadValue (integer parameter out of range for operation) #216
Comments
This error can be reproduced using
We can observe an apparent inconsistency when running A) List matching fonts:
B) List attributes as well:
C) List properties as well:
The issue seems related to the fonts found via the The issue happens in Monterrey 12.2.1; I think the title should be changed to "X_OpenFont BadValue (integer parameter out of range for operation)" |
Can you explain how this is related to /opt/X11/share/system_fonts? |
#217 (dupe) has some sample code to try and reproduce this. |
Several weeks ago, I install I have no idea about the detail of this problem. orz Maybe @medranocalvo can explain. |
I think I see one possible issue. We don't wait for font caching to complete before starting up the server. In both places that we cache fonts (system and user), we push the caching into the background. I don't remember why we did that, but it seems like a clear race condition.
I actually just hit this myself, and it was resolved by running |
This did not work for me on my M1 Macbook Pro running the latest 12.4 Monterey. If I select any of the system ttf fonts from /opt/X11/share/system_fonts in xfontsel or try to use them for an xterm I get:
Checking the current settings:
Trying the above solution:
Still gives the same error when I attempt to select the Monaco font in |
@nello What is the invocation you are using? What is the output of |
The output of It does contain Monaco fonts:
|
I can't select Monaco in |
@nello Can you give me your exact invocations? |
Hi, thanks for looking at this. In .Xresources, this seems to work:
This (and every variation of it I have tried!) does not -
Is that what you mean by "invocations"? |
By invocations, I want to know how you are invoking |
Hello @jeremyhu,
The only relation is that the issue stops manifesting when removing Changing the font path as you suggested does not help (commands are lines starting with
The font comes from
I initially thought it was related to the TTC format, but other fonts such as "Optima.ttc" do not produce the error. Hope this helps. Let me know if I can help. (Sorry for the late answer.) |
I type Screen.Recording.2022-06-20.at.20.June.19.56.54.mov |
Please confirm if I'm wrong, but it looks like this is an old issue and not a recent regression. I'm seeing this occur with XQuartz 2.7.11 running on macOS 10.13. |
I'm able to repdouce it on an Ubuntu machine as well with Unfortunately, I'm having some troubles getting xscope working on darwin right now, but on Ubuntu, here's what I see:
I'm going to start digging around in the server sources to see what might be going on... |
Thanks Jeremy. I didn't manage to get to this yesterday, so apologies. I can confirm that it does seem to be an old bug though. I've reproduced now on an older machine. |
I also started a thread on xorg-devel to see if anyone there had some thoughts: https://lists.x.org/archives/xorg-devel/2022-July/058848.html |
This issue also causes crashes in other applications that use tk, see https://core.tcl-lang.org/tk/tktview?name=36e379c01b We could also reproduce the issue on our own machine (apple silicon based with Big Sur, Xquarts 2.8.3). To further diagnose the problem we used the following shell script to detect fonts that are giving errors:
This script found 10000+ "good" fonts and 477 "bad" ones. See problemFonts.txt for the latter ones. All of the problematic fonts seem to have the pattern "0-0-0-0-p-0" or "0-0-0-0-m-0", which seem to be much rarer in the good fonts. |
On Ventura we also detected two fonts that give errors but have a different pattern: -misc-gb18030 bitmap-thin-r-ultracondensed--0-0-75-2147483647-c-0-cns11643-2 |
Hi, sorry no. It's not the only one, just the particular one I wanted to use. For me it seems that 5-10% of all fonts seem to blow up.
… On 27 Jan 2023, at 4:52 pm, Jeremy Huddleston Sequoia ***@***.***> wrote:
@nello <https://github.com/nello> Is Monaco the only font impacted by this issue? We can add it to the list of fonts skipped when setting up the font dir symlinks like we did for NISC18030.ttf in #304 <#304>
—
Reply to this email directly, view it on GitHub <#216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHL3WV5AGMPR6KLZYBMAQTWUNPCNANCNFSM5GJLXMGQ>.
You are receiving this because you were mentioned.
|
Are the problematic ones all Apple system fonts, or are some of the problematic ones from Xorg? If I can show this happening with an Xorg-provided font, that might help get some traction... |
I'll have to get back to you, sorry. I had basically abandoned this (it's been a while!) but will take a look tomorrow. I think you may be onto something though
… On 27 Jan 2023, at 5:45 pm, Jeremy Huddleston Sequoia ***@***.***> wrote:
Are the problematic ones all Apple system fonts, or are some of the problematic ones from Xorg?
—
Reply to this email directly, view it on GitHub <#216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHL3WWFJULSFVFL376DWF3WUNVJTANCNFSM5GJLXMGQ>.
You are receiving this because you were mentioned.
|
The file problemFonts.txt in our update above has a list of fonts that give errors when queried with xlsfonts -ll -fn , would that be helpful? That file is for Big Sur but we also have lists for Lion and Ventura if that would be helpful. |
While implementing the X protocol in Kotlin/JVM, I ran in the same problem. The bad-value error gives the font id. But as I learnt here, it is an internal server problem. Is there a solution in sight? |
…a Tk problem, but a known [XQuartz/XQuartz#216] problem.
…a Tk problem, but a known [XQuartz/XQuartz#216] problem.
…a Tk problem, but a known [XQuartz/XQuartz#216] problem.
Hi, I'm trying to use tlmgr's gui which needs X window, so I installed XQuartz 2.8.1 via homebrew.
When I tried to open tlmgr's gui, I got this error message:
I have searched and found issue #97 but it seems different (I really don't know 😢 xlsfonts and xclock seems work fine)
Please let me know what information I need to provide to solve this problem.
My environment:
Any help will be appreciated.
The text was updated successfully, but these errors were encountered: