Bug 3348 - GNOME theme-selector-capplet Core Dumps After Choosing Custom Font
Summary: GNOME theme-selector-capplet Core Dumps After Choosing Custom Font
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: distribution
Version: 6.0
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-06-08 21:38 UTC by orsingerc
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-06-29 14:29:25 UTC
Embargoed:


Attachments (Terms of Use)

Description orsingerc 1999-06-08 21:38:18 UTC
Ran the theme-selector-capplet using the control-center
program (IOW, the normal way). Chose "custom font" option,
and set the font to a larger pitch size. After doing this,
the capplet generates a .gtkrc file and exits. Trying to run
the capplet again afterward causes the capplet to core dump
without displaying an information in the control-center
window. Removing the .gtkrc file allows the capplet to run
again.

If you set the "Metric" radio buttons in the "Pick A Font"
window to "pixels" rather than "points", the capplet works
properly. Below is a copy of one of the .gtkrc files created
by the capplet in "points mode", which caused the capplet to
core dump subsequently.

The bug here is that the capplet creates a .gtkrc file that
causes the capplet to core dump on subsequent runs.


# -- THEME AUTO-WRITTEN DO NOT EDIT
include "/usr/share/themes/Default/gtk/gtkrc"

style "user-font"
{
font="-adobe-helvetica-medium-r-normal-*-*-140-*-*-p-*-iso859-1"
}

widget_class "*" style "user-font"

include "~/.gtkrc.mine"

# -- THEME AUTO-WRITTEN DO NOT EDIT

Comment 1 orsingerc 1999-06-08 21:40:59 UTC
Couldn't edit the .gtkrc file properly. the end of the string is
actually:

iso8859-1

rather than

iso859-1

Comment 2 Jay Turner 1999-06-29 14:29:59 UTC
Try upgrading to the latest GNOME packages available from the updates
site and then reopen this bug if you are still having problems.


Note You need to log in before you can comment on or make changes to this bug.