- Support: sr #106966, Problems setting fonts and sizes...


sr #106966: Problems setting fonts and sizes in Terminal

Submitted by:  None
Submitted on:  Fri Aug 7 20:22:36 2009  
Category: NonePriority: 5 - Normal
Severity: 3 - NormalStatus: None
Privacy: PublicAssigned to: None
Originator Email: -unavailable-Open/Closed: Open
Operating System: GNU/Linux

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

Please log in, so followups can be emailed to you.


(Jump to the original submission Jump to the original submission)

Tue Dec 8 01:01:43 2009, comment #7:

The following are results of tests on both the old tarball version (0.9.5) and a new version (extracted from CVS on 6th December 2009), using libobjc versions 4.1 and 4.4:

Old source, libobjc version 4.1 -

Attempting to change fonts using the Preferences
panel causes to crash with a Seg fault.

New source, libobjc version 4.1 -

Attempting to change fonts using the Preferences
panel causes to crash with a Seg fault.

Old source, libobjc version 4.4 -

Changing fonts from DejaVu Sans 12 to FreeSans 16
works OK - no crash. On bringing up a new
window, the correct font is displayed. The new fonts
are recorded in .GNUstepDefaults.

New source, libobjc version 4.4 -

Changing fonts using the Preferences panel no longer
causes a Seg Fault, however it is ineffective - the
new details are entered in the dialogue box but:

1. The font used in a new Terminal window is still
the old one; and

2. The new fonts do not seem to get saved in
.GNUstepDefaults, and are lost after
is closed and restarted.

Richard Stonehouse <r_stonehouse>
Wed Nov 25 09:09:13 2009, comment #6:

The bug was a problem in method invocation.

It is a problem in libobjc and was fixed around 2007. So gcc 4.1.2 is affected but also gcc 4.2.1 I am using. On some platforms the bug does not manifest though.

One solution (I did not test myself) is to install "our" libobjc (1.6.0 is latest, I guess). It installs inside the GNUstep hierarchy and does not affect the rest of the system.
This is the way gcc 2.95 can be used for example.
After installing it, base needs to be reconfigured.

Otherwise you could try the latest SVN head or nightly tarball which contains a workaround in for older libobjc.

Terminal was fixed too since it had some strange workaround for this bug too which was removed. Use the version in GAP CVS head please.

I cannot close the bug here since I am not a bug manager. Future requests and bugs should be done in GAP.

Sat Nov 21 23:55:00 2009, comment #5:

Backtrace and other gdb output attached, as requested.

(file #19104)

Richard Stonehouse <r_stonehouse>
Thu Nov 19 15:29:22 2009, comment #4:

The distro is openSUSE version 10.2 (a bit old, I know).

The compiler is gcc:

gcc -v
Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=i586-suse-linux
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)

libffi is used:


In case relevant, the objc versions are:


The software is compiled for i586 32-bit (the processor is actually an AMD Athlon XP1700+)

gnustep-back is built with the art backend

I'll try to get the backtrace and other diagnostic information you request but will need to rebuild with debugging symbols - presumably the GNUstep libraries as well as

I note your request to report stuff under gap rather than Terminal and will do so when initiating future reports - should I re-raise this one under gap or continue under the present filing?

Richard Stonehouse <r_stonehouse>
Wed Nov 18 18:58:27 2009, comment #3:

Please let me add that Terminal is maintained inside GAP now, thus post bugs related to it there.

I cannot reproduce your problem on any Linux box i tried and so cannot Gregory and Fred.
Please let us know:
- compiler
- if ffcall or libffi is used
- architecture and if 32 or 64 bits
- backend (cairo,art,xlib)

anything else which might be relevant. I suppose you are under Suse linux.

If you could provide a backtrace. Also, try when you stop due to the crash, to walk up the stack of one level ("up 1" in gdb) and print out the sender ("po sender").

thank you.

Riccardo Mottola <rmottola>
Sun Nov 15 21:16:05 2009, comment #2:

Regarding the first issue:

It seems that others have had the same problem - see:


the latter of which says "As I can see this is a bug on Font Panel. I can reproduce this problem on others apps."

I'm not clear whether this means it is a known problem or whether it ought to be reported.

I am using the stable versions, gnustep-make-2.2.0, base-1.18.0, and gui- and back-0.16.0.

Regarding the second issue: agreed, I now see I was using the wrong keys. When I use the correct keys, setting the fonts directly (in the non-recommended way) works fine.

Richard Stonehouse <r_stonehouse>
Sat Nov 14 22:25:15 2009, comment #1:

I do not fully follow this bug.

I think there are two different issues:

First, you try to set your font using the Preferences panel. It does not work for you, but I tried on several different machines and configurations, so I think something is wrong at your side. I tried on xlib, art and cairo backends...

Failing that you try to directly write the fotn preferences into terminal using "defaults" command line tool or a similar approach. THis sets the font for everything and not just the console. I would not consider this a bug, since it is not the recommended way and you are probably not setting the correct key in the domain.

Riccardo Mottola <rmottola>
Fri Aug 7 20:22:36 2009, original submission:

* Attempting to set the font using the Preferences dialogue;
on clicking 'Set' in the Font Panel, Terminal fails, e.g.:

2009-08-07 20:03:51.022 Terminal[12097] NSFont <NSFont: 0x82988b8> FreeMono 16.000 0.000 0.000 16.000 0.000 0.000 N S 6 info <FTFontInfo: 0x8296380> size 16 {x = 2; y = -2; width = 4; height = 12} 1
Segmentation fault

* If a font is set in the user's GNUstep defaults:

- if it is invalid, Terminal complains about it
(correctly!); but

- if it is valid, Terminal just ignores it and uses
the font it would have done anyway;

- however, setting a font size in defaults does
take effect in the terminal window.

* Setting a font size seems to apply it to the menus and
dialogues as well as the terminal data (but, for menus,
can be over-ridden by declaring a specific menu font
and size). I think menu and dialogue fonts should be
standard across all applications, not affected by
application settings.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):

Attached Files
file #19104:  typescript added by r_stonehouse (11kB - application/octet-stream)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by r_stonehouse (Posted a comment)
  • -unavailable- added by rmottola (Posted a comment)
  • -unavailable- added by None (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat Nov 21 23:55:00 2009r_stonehouseAttached File-=>Added typescript, #19104

    Back to the top

    Powered by Savane 3.1-cleanup