Created attachment 1154 [details] fontforge terminal output Fontforge crashes in KDE4.6.5 with or without opening document as in enclosed massage. Fontforge runs perfect in GNOME 2.32.1. What's the problem?
Target Milestone: --- => Mageia 2
CC: sysadmin-bugs => (none)Component: Release (media or process) => RPM PackagesSource RPM: (none) => fontforge
what is the output of ls -l /home/user/Munkaasztal/some* ? "existed in the font list, but when I asked for it there was nothing." something is wrong with your font maybe
GNOME did not have any error as the fonts are concerned. Even only on starting Fontforge the same error occures before quitting. I'm regenerating font caches (mkfontscale, mkfontdir, fc-cache -r -v) and I'll change to KDE to look at the developments. These fonts (as report says) are located in system's partition.
I figured out the problem. As I think. Two parts. The first problem is in setting of Fontforge. It refers to a font exists in the user directory. All programs (even the Fontforge too) can see it, but somehow forgets in KDE enviromment. The other part of the problem that the user font cache files are created for the system fonts also contain references, but the fontscale.dir files (located in the system partition) are empty, so (for KDE) can not identify them. I do not understand why the problem occurs in KDE and GNOME why not, as I know Fontforge is an X-specific program. No bussiness with QT or GTK+. Or yes? I think the problem is in Fontforge itself, which in this context does not like the KDE environment. I read several pages, for example Ubuntu and Debian bug reports. As for me to close the thread.
Ok thanks, usually, we keep the upstream bug open. So feel free to add the a link here.
Keywords: (none) => UPSTREAM
cc'ing maintainer @ Anssi Do you read a fontforge mailinglist? I don't manage to find the upstream bug report.
CC: (none) => anssi.hannula, marja11
Does anyone have a link to an upstream bug report or mailing list thread? Is this bug valid in current cauldron (with cauldron KDE version), too?
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX