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 81677 - impossibel to change font in "appearance" tab
impossibel to change font in "appearance" tab
Status: RESOLVED FIXED
Product: Sawfish
Classification: Deprecated
Component: Config Tool
pre-1.3.x
Other other
: High major
: 1.5.x
Assigned To: John Harper
sawfish QA Team
Depends on:
Blocks:
 
 
Reported: 2002-05-13 20:51 UTC by Alexander Kirillov
Modified: 2009-08-16 15:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alexander Kirillov 2002-05-13 20:51:35 UTC 
I tried to change the default font used by Sawfish. I middle-cliked on the
desktop background, selected cuatomize->appearance. It shows theme name
(Crux) and default font (fixed). I tried to change font to something nicer 
by hitting the "browse" button and selecting LuciduxSans, 14  pt - which
immediately gives an error message:


While changing default-font:
Error: no such font, LuciduxSans 14fixed

Apparently, the system *appends* the font name to this "fixed"

I tried to manually enter font name in the box - 
- but as soon as I start erasing "fixed" an error message pops up: 

While changing default-font:
Error: no such font, fixe

Apparently, the capplet tries to "instant apply" as I erase, which results
in the error. 


SO how on Earth am I supposed to change the default font? 


PS. This is with the snapshot 20020509
Comment 1 Luis Villa 2002-05-21 04:41:15 UTC 
Is the super-instant-apply-ness of this dialogue related to the same
in bug 81723, John?
Comment 2 John Harper 2002-05-21 17:34:07 UTC 
I don't think they're related enough to dup it.

But I think I did fix this recently. Can't remember if I committed the
change or if it's still sitting in my local copy..
Comment 3 Joseph Carter 2002-08-25 21:58:25 UTC 
Not fixed in 1.1, FWIW.
Comment 4 L3ECH 2003-04-23 07:23:58 UTC 
using sawfish 1.3, and this bug is not fixed.
Comment 5 Andrea Vettorello 2008-01-21 10:05:59 UTC 
I could not reproduce it with Sawfish 1.3.1 so i'm going to close it. Feel free to reopen it if it's still present.