Bug 28265
Summary: | (xset) broken - doesn't allow +fp properly | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Michal Jaegermann <michal> |
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED WORKSFORME | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 1.0 | CC: | katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-19 17:54:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2001-02-19 05:12:42 UTC
xset +fp has been broken ever since XFree-4.0. I only now realized that all these "Could not init font path element" errors I reported stem from that that 4.0.2 server in question does not load "type1", or "freetype", or "speedo" modules unless explicitely asked to. Once corresponding requests are added in Modules section of a cofiguration file then errors disappear and fonts in question do show up. This is a bit surprising change of a behaviour in conparison with earlier versions of X and files produced by configuration tools do not have these "load" statements. Also AbiWord when it cannot find its fonts behaves in the most obnoxious manner (SIGSEGV and the like). Are you running xfs at boot time? Make sure xfs is running. Yes, I do run xfs at a boot time, or I specify FontPath in my configuration file. This does not matter. But see my comments from 2001-02-23. I run into the same problem with fonts also on x86 with 4.0.2 and the solution is the same. One has to ask for modules like "type1" or "freetype" explicitely in a configuration file; otherwise they are not loaded. Ok, I think I grok what you're saying now. I just reproduced exactly what you are claiming on x86, so it is not specific to alpha. I'll see if we can have Xconfigurator do this automatically, as it is brain damaged the way it is now IMHO. Thanks very much for reporting this stuff Michal, and keeping up with new info, etc. It helps us out a lot! I'm going to see if we can solve this now in a useful way. Thanks again. I've researched this a bit and here is what it appears you need to do. If you are using xfs, things should work fine (XFree86 4.0.3), if you are not using xfs then you need to configure your XF86Config to properly load the modules. You shouldn't need the modules if you are using xfs which is our default behaviour. xset thus doesn't contain a bug WRT the problem you're having. The problem is related to configuration/default configuration issues. I don't see it as a bug anymore however we will put some commented out lines in the default config files to ease configuration. If you're not satisfied with this solution, please open a new bug report against Xconfigurator, as ultimately that is what creates the configs. For obvious reasons the report could not be about XFree86 4.0.3; but a configuration file on machine in question always had Section "Files" FontPath "unix/:7100" EndSection |