After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 384876 - No Fonts are displayed *anywhere*: main screen, dialogs, drop-down menues, etc
No Fonts are displayed *anywhere*: main screen, dialogs, drop-down menues, etc
Status: RESOLVED NOTABUG
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.10.x
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 433172 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-11 23:18 UTC by Alfredo Lacis
Modified: 2007-12-26 04:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of Font Rectangles Bug (82.49 KB, image/png)
2006-12-11 23:22 UTC, Alfredo Lacis
Details
Showing Gimp using Arial(?) after changing my fixed system fron from .ttf to .fon (96.93 KB, image/png)
2007-01-15 00:26 UTC, Alfredo Lacis
Details
Screenshot of ProFont Vs Courier (166.10 KB, image/png)
2007-01-16 04:06 UTC, Alfredo Lacis
Details
Display Settings:Appearance:Advanced : selection of ProFont (18.50 KB, image/png)
2007-01-16 23:42 UTC, Alfredo Lacis
Details
screenshot of Control Panel with ProFontWindows as Icon font (103.29 KB, image/png)
2007-01-17 00:06 UTC, Tor Lillqvist
Details
Set To Courier New (16.02 KB, image/png)
2007-01-17 03:44 UTC, Alfredo Lacis
Details
Set back to ProFont TTF version - Now works OK! (14.75 KB, image/png)
2007-01-17 03:48 UTC, Alfredo Lacis
Details
Set to old ProFont TTF version (which had a different scaling size) - it's OK now, too! (15.53 KB, image/png)
2007-01-17 03:50 UTC, Alfredo Lacis
Details

Description Alfredo Lacis 2006-12-11 23:18:29 UTC
No Fonts are displayed *anywhere*: main screen, dialogs, drop-down menues, etc.

All characters appear as a string of rectangles.

1. I've checked the open bugs for 'font' but nothing appears to match this bug.

2. I tried reinstalling the latest, stable, GTK & GIMP, but the problem remains.

I'd like to paste a screenshot, but Bugzilla won't let me.
Comment 1 Alfredo Lacis 2006-12-11 23:22:19 UTC
Created attachment 78174 [details]
Screenshot of Font Rectangles Bug

Sorry: I can attach a screenshot in follow-up comments.
Comment 2 Sven Neumann 2006-12-11 23:43:26 UTC
See bug #345267.
Comment 3 Sven Neumann 2006-12-15 09:28:21 UTC
We definitely need more information. What locale are you using? What's the system font? What else could you tell us about your system?
Comment 4 Michael Schumacher 2007-01-14 15:01:27 UTC
Alfredo, this will not be solved if you don't answer the questions.
Comment 5 Alfredo Lacis 2007-01-15 00:15:08 UTC
Sorry, didn't see comment #3.

I played around with the system fonts this morning.

I was using the fixed-spacing TrueType Font "ProFont for Windows" for all my dialogs, available here:
http://www.tobiasjung.net/download.php?file=MProFont.zip

This was a .TTF, so I decided to change to the .fon version instead http://www.tobiasjung.net/download.php?file=profontwin.zip

Everything now displays correctly.

Only GIMP had a problem with this .TTF: every other application, and I have many including cross-developed applications like:
= OpenOffice, 
= Rowley's CrossStudio for ARM (which uses QT), 
= JEdit (Java), 
= Vim, 
= Cygwin-X, 
= Code::Blocks, 
etc.
Comment 6 Alfredo Lacis 2007-01-15 00:26:28 UTC
Created attachment 80285 [details]
Showing Gimp using Arial(?) after changing my fixed system fron from .ttf to .fon

Gimp has reverted to using some sans serif font (Arial?) after I changed my system font from .ttf to a .fon.
Comment 7 Sven Neumann 2007-01-15 07:05:13 UTC
Whatever is causing this, it's most certainly not a GIMP problem and we can't do anything about it. If you want to see this being addressed, you should check other GTK+ applications on your system and eventually file a bug report against GTK+.
Comment 8 Michael Schumacher 2007-01-15 09:50:33 UTC
Problems with the Profont fonts are known (at least they have been the cause for similar symptoms in the past). Seems like http://www.tobiasjung.net is the website of the author, maybe he knows about the problem already.
Comment 9 Michael Schumacher 2007-01-15 22:44:57 UTC
Comments from a scribus developer:

"that is a bitmap font in a TTF wrapper
why someone would use it as a GUI font.. eeew"

Apparently there are some other problems as well.

There's code to reject broken fonts in Scribus' scfonts.cpp, http://docs.scribus.net/devel/scfonts_8cpp-source.html
(in SCFonts::AddScalableFont, I think)
Comment 10 Tor Lillqvist 2007-01-15 23:31:37 UTC
When you say you had the "ProFontWindows" as system font, what exactly do you mean? Did you select it in Display Settings:Appearance:Advanced as the font for Message Boxes? What size did you select, 8? I did that, but couldn't reproduce the problem. (GTK+ apps did not use this font even if set gtk-theme-name="MS-Windows" in gtkrc, they just printed warnings "Pango-WARNING **: couldn't load font "ProFontWindows 8, falling back to Sans 8".) (To see such warnings it's easiest to use for instance gtk-demo.exe and not GIMP, as GIMP firstly normally is a GUI executable and it's stderr doesn't show up even if you start it from a command prompt, and secondly, it does some special tricks and these warnings go somewhere else even if you change it into a console executable...)
Comment 11 Alfredo Lacis 2007-01-16 04:03:50 UTC
Note that there are 2 ProFontWindows fonts.
The one I had trouble with GTK/GIMP was the .ttf version.
I changed to the .fon version, and GIMP now displays text/dialogs/etc correctly.

The .fon version is probably responsible for the "falling back to Sans..." message: remember that I said that GIMP dialogs now look like Arial.

(As to "why someone would use it as a GUI font.. eeew": it is only a wise man who knows that he knows little. 
Tobias Jung especially designed ProFont as a tiny but legible font for text editors: it packs tightly, is fixed-width, and is good for 1<>l, 0<>O and others. It's also good for directory listings, either GUI or text(dir or ls).
See http://www.tobias-jung.de/seekingprofont/ Another tiny similar font is Sheldon.
See attached screenshot of ProFont Vs Courier)
Comment 12 Alfredo Lacis 2007-01-16 04:06:01 UTC
Created attachment 80356 [details]
Screenshot of ProFont Vs Courier

The clarity of Profont, even though its packing density is higher than Courier, is also clearer.
Comment 13 Sven Neumann 2007-01-16 07:36:04 UTC
Can you please reassign this bug to GTK+ or Pango. It is in no way a GIMP bug.
Comment 14 Tor Lillqvist 2007-01-16 10:14:15 UTC
> Note that there are 2 ProFontWindows fonts

Yes I know, as I said in comment #10.

Instead of trying to diagnose the mechanisms that cause the symptom you are seeing yourself ("is probably responsible for"), or bragging about the clarity of ProFont (which is absolutely irrelevant from this bug's point of view), why didn't you answer the direct question I asked? I repeat:

When you say you had the "ProFontWindows" as system font, what exactly do you
mean? Did you select it in Display Settings:Appearance:Advanced as the font for
Message Boxes? What size did you select, 8?
Comment 15 Tor Lillqvist 2007-01-16 10:18:40 UTC
Also please note that unless you cooperate by giving the information asked for, not much can be done about this problem. As I said in comment #10, I couldn't reproduce it myself just by guessing what you exactly had done.
Comment 16 Alfredo Lacis 2007-01-16 23:42:36 UTC
Created attachment 80438 [details]
Display Settings:Appearance:Advanced : selection of ProFont

(In reply to comment #14)
> When you say you had the "ProFontWindows" as system font, what exactly do you
> mean? Did you select it in Display Settings:Appearance:Advanced as the font for
> Message Boxes? What size did you select, 8?
Yes, please see attachment gtk_screenshot_5.png
I selected 9 most of the time, which is the same width as 8, just a pixel taller which is nicer in menus, Windows Explorer, etc.  (I usually use 8 where I want more lines per window, e.g. text editors, but that doesn't change Windows settings.)

> ... or bragging about the clarity
> of ProFont (which is absolutely irrelevant from this bug's point of view),
*I* know it's irrelevant, but I was humiliated and I lost face because I had chosen a fixed font (I was not bragging(after all, I didn't design it): I chose the font for very good reasons), and I do not have to take abuse like "ewwww" for my actions. I am not a slave, and I will not stand here quietly and be abused. <rant removed>. Please feel free to edit, mediate, truncate or remove this second comment, or the whole thread if you like. I was trying to point out a problem, and I get abused and humiliated for my effort.
Comment 17 Tor Lillqvist 2007-01-17 00:06:31 UTC
Created attachment 80460 [details]
screenshot of Control Panel with ProFontWindows as Icon font

If I set ProFontWindows to be the Icon font as in your screenshot, all icon text disappears from Explorer ;) (See screenshot above.) If I set it as the Message Boxes font, all text disappears from the application "GroupWise", which seems to use that font for all its text... There is something seriously wrong with ProFontWindows, it seems.
Comment 18 Alfredo Lacis 2007-01-17 03:44:37 UTC
Created attachment 80476 [details]
Set To Courier New

I set all Windows fonts to Courier New & everything OK: see GIMP screenshot.
Comment 19 Alfredo Lacis 2007-01-17 03:48:29 UTC
Created attachment 80477 [details]
Set back to ProFont TTF version - Now works OK!

Set back to ProFont TTF version, now works OK!
Comment 20 Alfredo Lacis 2007-01-17 03:50:09 UTC
Created attachment 80478 [details]
Set to old ProFont TTF version (which had a different scaling size) - it's OK now, too!

Just for curiosity purposes, I set Windows to old ProFont TTF version (which had a different scaling size) - it's OK, too!
Comment 21 Alfredo Lacis 2007-01-17 04:07:34 UTC
Now, I cannot get GIMP/GTK to fail... everything I try is OK!  See Comment #18, Comment #19, Comment #20.  Each font I tried, I did this:
= change the Windows settings to Courier New, 
= delete the old font
= restart Windows
= install the new font to be tested
= change the Windows settings to the new font
= start GIMP
I have not see the problem in Comment #17: my Explorer & other windows all appear OK. I don't know what to try now.
Comment 22 Tor Lillqvist 2007-01-17 10:01:26 UTC
Hmm, so now everything works for you?

(And I still haven't been able to either reproduce the original problem, or take ProFontWindows into use in GTK+ apps.)

Is it really necessary to restart Windows for font setting changes to properly take effect? I will have to do further testing in a virtual machine then.

I notice there are two versions of the TrueType ProFontWindows on the tobias-jung site: MProFont.zip and ProFontWinTweaked.zip. I used the MProFont.zip one, did you use the other one?
Comment 23 solo turn 2007-02-07 00:23:07 UTC
i get a similar problem with the new debian testing, with all fonts except "kochi gothic" and one or two others:

$ gedit --g-fatal-warnings
Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Bitstream Vera Sans 12'

Backtrace was generated from '/usr/bin/gedit'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1493940544 (LWP 9605)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1493940544 (LWP 9605))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 pango_shape
    from /usr/lib/libpango-1.0.so.0
  • #10 pango_layout_set_width
    from /usr/lib/libpango-1.0.so.0
  • #11 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #12 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #13 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #14 pango_fc_font_create_metrics_for_context
    from /usr/lib/libpangoft2-1.0.so.0
  • #15 pango_cairo_fc_font_get_type
    from /usr/lib/libpangocairo-1.0.so.0
  • #16 pango_font_get_metrics
    from /usr/lib/libpango-1.0.so.0
  • #17 pango_context_get_font_description
    from /usr/lib/libpango-1.0.so.0
  • #18 pango_fontset_simple_size
    from /usr/lib/libpango-1.0.so.0
  • #19 pango_fontset_foreach
    from /usr/lib/libpango-1.0.so.0
  • #20 pango_context_get_metrics
    from /usr/lib/libpango-1.0.so.0
  • #21 gtk_entry_size_request
    at gtkentry.c line 1236
  • #22 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #28 do_size_request
    at gtksizegroup.c line 592
  • #29 _gtk_size_group_compute_requisition
    at gtksizegroup.c line 788
  • #30 IA__gtk_widget_size_request
    at gtkwidget.c line 2709
  • #31 gtk_font_selection_load_font
    at gtkfontsel.c line 1129
  • #32 gtk_font_selection_select_style
    at gtkfontsel.c line 927
  • #33 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #37 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #38 _gtk_tree_selection_internal_select_node
    at gtktreeselection.c line 1490
  • #39 gtk_tree_view_real_set_cursor
    at gtktreeview.c line 11315
  • #40 IA__gtk_tree_view_set_cursor_on_cell
    at gtktreeview.c line 11443
  • #41 IA__gtk_tree_view_set_cursor
    at gtktreeview.c line 11395
  • #42 set_cursor_to_iter
    at gtkfontsel.c line 645
  • #43 gtk_font_selection_show_available_styles
    at gtkfontsel.c line 876
  • #44 gtk_font_selection_screen_changed
    at gtkfontsel.c line 612
  • #45 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib/libgobject-2.0.so.0
  • #46 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #47 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #48 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #49 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #50 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #51 do_screen_change
    at gtkwidget.c line 5012
  • #52 gtk_widget_propagate_hierarchy_changed_recurse
    at gtkwidget.c line 5036
  • #53 _gtk_widget_propagate_hierarchy_changed
    at gtkwidget.c line 5076
  • #54 IA__gtk_widget_set_parent
    at gtkwidget.c line 4526
  • #55 IA__gtk_box_pack_start
    at gtkbox.c line 390
  • #56 gtk_font_selection_dialog_init
    at gtkfontsel.c line 1357
  • #57 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #58 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #59 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #60 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #61 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #62 gtk_font_selection_dialog_new
    at gtkfontsel.c line 1397
  • #63 gtk_font_button_clicked
    at gtkfontbutton.c line 725
  • #64 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #65 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #66 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #67 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #68 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #69 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #70 IA__gtk_button_clicked
    at gtkbutton.c line 845
  • #71 gtk_real_button_released
    at gtkbutton.c line 1380
  • #72 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #73 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #74 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #75 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #76 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #77 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #78 IA__gtk_button_released
    at gtkbutton.c line 837
  • #79 gtk_button_button_release
    at gtkbutton.c line 1273
  • #80 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #81 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #82 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #83 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #84 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #85 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #86 gtk_widget_event_internal
    at gtkwidget.c line 3751
  • #87 IA__gtk_propagate_event
    at gtkmain.c line 2195
  • #88 IA__gtk_main_do_event
    at gtkmain.c line 1424
  • #89 gdk_event_dispatch
    at gdkevents-x11.c line 2291
  • #90 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #91 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #92 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #93 IA__gtk_main
    at gtkmain.c line 1003
  • #94 main
  • #0 __kernel_vsyscall

Comment 24 Tor Lillqvist 2007-02-07 00:27:19 UTC
Problems with GTK+ or Pango in Debian are totally unrelated to problems with GTK+ or Pango on Win32, though. Sigh.
Comment 25 solo turn 2007-02-07 00:34:23 UTC
why? it happens also with windows fonts on debian ...  but ok ... ill look for the bug with linux :)


Comment 26 Sven Neumann 2007-04-25 06:10:11 UTC
*** Bug 433172 has been marked as a duplicate of this bug. ***
Comment 27 Cody Russell 2007-12-26 04:12:21 UTC
Since Alfredo said this is working I'm going to go ahead and close this bug.