Fatal font error when opening Glimmr Canvas Editor

[GoogleCodeExporter]

What steps will reproduce the problem?
1. gargoyle 
2. (navigate to GCE and open file)
3. Immediate failure

What is the expected output? What do you see instead?

I'm not sure what the expected output is, as I've never seen it work yet.

Here is the output I'm getting:

$ gargoyle 
fatal: FT_New_Face: LiberationMono-Regular: 0x1
Aborted

What version of the product are you using? On what operating system?

OS: Linux Mint, 10
Compiled Gargoyle from source

Please provide any additional information below.

Other samples from Glimmr seem to work fine, though I haven't tried them all.

http://code.google.com/p/glimmr-i7x/
I tried both the most recent release and the version 2 release - both gave the 
same error.

I can also get the same error if I use the git program directly on the file, so 
I assume the problem is stemming from git, not gargoyle.

I am attaching a strace from a failed run. Hopefully that helps slightly. I'd 
be willing to provide anything else that would be of assistance.

Original issue reported on code.google.com by thecsapp...@gmail.com on 9 Mar 2011 at 6:03

Attachments:

• gargoyle.strace

[GoogleCodeExporter]

Can you check to see if you have the Liberation fonts package installed? That 
error should only appear if it can't find the font file.

Did you compile Gargoyle with the BUNDLED_FONTS option set to no? Ordinarily it 
should use the bundled Luxi Mono font as a fallback.

Original comment by bcressey@gmail.com on 9 Mar 2011 at 3:46

• Changed state: Accepted

[GoogleCodeExporter]

Oh, I think it's an issue with the "Basic Floorplan Example Toolkit.ini" file 
that comes with Glimmr. It has the old style mono* directives instead of using 
the new system font loading code.

Try removing the monor - monoz and propr - propz lines, and replacing them with 
this.

monofont    Liberation Mono
propfont      Linux Libertine O

Original comment by bcressey@gmail.com on 9 Mar 2011 at 3:51

[GoogleCodeExporter]

The error should also not happen if you have a current copy of garglk.ini in 
one of the default locations - /etc/garglk.ini or ~/garglk.ini.

The propfont / monofont directives in that file will override any of the older 
prop* / mono* entries.

Original comment by bcressey@gmail.com on 9 Mar 2011 at 11:23

[GoogleCodeExporter]

Ah, yes that seemed to fix it. 

That solution would not have occurred to me, thanks.

Perhaps I should open a bug report with the Glimmr people instead. Has this 
been a problem long?

Original comment by thecsapp...@gmail.com on 9 Mar 2011 at 11:54

[GoogleCodeExporter]

Opening a bug report with Glimmr makes sense - those lines can be removed from 
the ini file without affecting the Canvas Editor.

During last year's development cycle, the font handling code changed in a 
number of ways, and Glimmr happened to be released before the current method 
was fully baked.

As a result, it has a few vestigial traces of the old method, which would try 
to satisfy the prop* and mono* directives by loading a system font as a 
fallback option. This caused a lot of compatibility issues and ultimately had 
to be scrapped.

Original comment by bcressey@gmail.com on 14 Mar 2011 at 6:51

• Changed state: Fixed

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Just discovered this thread. The next release package for Glimmr will include 
an up-to-date .ini file. (The only reason for including a .ini is to eliminate 
the default margins; they are not appropriate in the canvas editor.)

Original comment by Ek.Temple@gmail.com on 19 Jan 2012 at 1:21