Version: 3.1.93 (CVS >= 20031111) (using KDE 3.1.93 (CVS >= 20031111), compiled sources) Compiler: gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-112.7.2) OS: Linux (i686) release 2.4.22 I upgraded my system from KDE-3.1.4 to 3.2 from 28.Nov. I start kcontrol (as root) and select the font-installer. On the right side of kcontrol it displays a list of fonts as fonts:/100dpi (or something like that), and then it starts to eat all my memory. I killed kcontrol as it reached about 500MB /proc/x/status showed shortly before my kill: [/disc/PACKAGES/KDE-3.2](:)# cat /proc/25164/status Name: kcontrol State: S (sleeping) Tgid: 25164 Pid: 25164 PPid: 1 TracerPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 32 Groups: 0 1 2 3 4 6 10 200 VmSize: 524188 kB VmLck: 0 kB VmRSS: 190108 kB VmData: 500364 kB VmStk: 84 kB VmExe: 4 kB VmLib: 20572 kB SigPnd: 0000000000000000 SigBlk: 0000000080000000 SigIgn: 8000000000001000 SigCgt: 00000003800104a8 CapInh: 0000000000000000 CapPrm: 00000000fffffeff CapEff: 00000000fffffeff This is always reproduceable. Also, on my first try to use this module I then killed the X-Server, and as a result, I have now in KDE different fonts displayed than before - _without_ changing anything, just by opening the font installer module!
Don't know if related, but in the konsole I started kcontrol from, I had a lot of kio (Filter): WARNING: KFilterDev::open: Couldn't open underlying device kio (Filter): WARNING: KFilterDev::open: Couldn't open underlying device kio (Filter): WARNING: KFilterDev::open: Couldn't open underlying device kio (Filter): WARNING: KFilterDev::open: Couldn't open underlying device kio (Filter): WARNING: KFilterDev::open: Couldn't open underlying device kio (Filter): WARNING: KFilterDev::open: Couldn't open underlying device Messages. Of what device is it talking ?
Subject: Re: font installer eats all my memory Hi, Just tried and I get the same results, :-( So, I modified the code and removed usage of KFilterDev, and just used zlib directly to open *.gz files - and everything seems fine. Can you "tar zxvf" the attatched filein kdebase/kcontrol/kfontinst/lib and rebuild/install (again!) kdebase/kcontrol/kfontinst - and let me know if it works for you. If so, then I'll send a patch to kde-core-devel for approval. thanks. Craig. Created an attachment (id=3511) kfi2.tar.gz
Subject: Re: font installer eats all my memory I have a problem compiling it. Did configure for complete kdebase, but still the following error. What am I missing ? CompressedFile.cpp: In method `char *CCompressedFile::getString (char *, unsigned int)': CompressedFile.cpp:172: `gzgets' undeclared (first use this function) CompressedFile.cpp:172: (Each undeclared identifier is reported only once for each function it appears in.)
Subject: Re: font installer eats all my memory Hmm... Loks like you're missing zlib - or its out of date, or is the "broken" one supplied with XFre86 - see http://lists.kde.org/?l=kde-core-devel&m=104720201123844&w=2 You could try downloading and compiling http://www.gzip.org/zlib/zlib-1.2.1.tar.bz2 ...the problems with using zlib before are what drove me to use KFilterDev. But this seems to be having problems. I'm interested to know if using zlib directly also solves these issues for you. Craig.
Subject: Re: font installer eats all my memory Also, looking at : http://lists.kde.org/?l=kde-devel&m=101406456609469&w=2 ...you may be able to just add: extern "C" { char* gzgets(gzFile file, char *buf, int len); } ...to CompressedFile.cpp -> try adding after all the #includes. Whixh zlib version are you using?
Subject: Re: font installer eats all my memory Or... Try using the attatched CompressedFile.cpp file (nees to be gunzip'ed) Created an attachment (id=3518) CompressedFile.cpp.gz
Subject: Re: font installer eats all my memory OK, I upgraded to zlib-1.2.1 and now it works ! No more eating memory. But one thing is still broken: I don't get previews for the fonts, except for TrueType fonts (e.g. for no 100dpi font I see a preview, but only on the top the name+size of the font). (and BTW: The preview should be displayed when I select another font, not on double-click) And if I select fonts:/default I get an error dialog "The process for the fonts protocol died unexpectedly." and in konsole (from where kcontrol was started) I see kio (Slave): slave died pid = 18712 And last point: this module always creates a XftConfig file in /usr/X11R6/lib/X11/, which leads to the behaviour that my X-Server uses different fonts than before! I want to keep my settings.
Subject: Re: font installer eats all my memory > OK, I upgraded to zlib-1.2.1 and now it works ! No more eating memory. Cool. I'll sending a posting to kde-core-devel about this issue. Perhaps I'm using KfilterDeve wrongly... > > But one thing is still broken: I don't get previews for the fonts, except > for TrueType fonts (e.g. for no 100dpi font I see a preview, but only on the > top the name+size of the font). Preview aren't supported yet for bitmap fonts - and haven't been for a while. If you want, open a wishlist item for this, and I'll see if I get time to do this. The name & size are displayed so that if you clicked on a bitmap font in the KDE file dialog you can know what it is. > > (and BTW: The preview should be displayed when I select another font, not on > double-click) ...it *is*. Is you system set up for double click? If so then that is to be expected - the behaviour should be the same as KDE's filedialog, I use its classes. > > And if I select fonts:/default I get an error dialog > "The process for the fonts protocol died unexpectedly." > and in konsole (from where kcontrol was started) I see > kio (Slave): slave died pid = 18712 Not sre what heppened here. What fonts do you have in "default"? Are there any TTF files? Its possible that the ioslave encountered a bad font - this is known to crash FreeType. > > And last point: this module always creates a XftConfig file > in /usr/X11R6/lib/X11/, which leads to the behaviour that my X-Server uses > different fonts than before! I want to keep my settings. Uh? How can it use different fonts? Are you sure this is not "Bug 69337: font installer removes xfs from XF86Config-4 file"? Your right that the XftConfig file is always created - but what harm can this do? All it will do is add your X directories to it - and your Xft directories to X. This way both have the same "view" of installed fonts. >
Subject: Re: font installer eats all my memory > > But one thing is still broken: I don't get previews for the fonts, except > > for TrueType fonts (e.g. for no 100dpi font I see a preview, but only on > > the > > > top the name+size of the font). > > Preview aren't supported yet for bitmap fonts - and haven't been for a > while. Hmmm ... I thought simply seetings this font on a widget will do the trick - no ? Doesn't Qt do the rest for you ? > If you want, open a wishlist item for this, and I'll see if I get > time to do this. The name & size are displayed so that if you clicked on a > bitmap font in the KDE file dialog you can know what it is. I'll do. This would greatly improve this module (from a usability standpoint). > > (and BTW: The preview should be displayed when I select another font, not > > on > > > double-click) > > ...it *is*. Is you system set up for double click? Yes. To _open_ files. > If so then that is to be > expected - the behaviour should be the same as KDE's filedialog, I use its > classes. It's not what one would expect. Have a look in the file-open dialog with automatic preview enabled. _Before_ you really open a file, you simply select it and you already see the preview. That should here be the same. It's just a preview, no action. > > > And if I select fonts:/default I get an error dialog > > "The process for the fonts protocol died unexpectedly." > > and in konsole (from where kcontrol was started) I see > > kio (Slave): slave died pid = 18712 > > Not sre what heppened here. What fonts do you have in "default"? Are there > any TTF files? Its possible that the ioslave encountered a bad font - this > is known to crash FreeType. - -rw-r--r-- 1 root root 0 Dez 2 17:03 Fontmap - -rw-r--r-- 1 root root 2 Dez 2 17:03 fonts.dir drwxr-xr-x 2 root root 4096 Dez 23 2001 ghostscript drwxr-xr-x 2 root root 4096 Dez 2 17:03 TrueType drwxr-xr-x 2 root root 4096 Dez 2 17:03 Type1 - -rw-r--r-- 1 root root 0 Dez 2 17:03 XftCache So yes, there are TrueType fonts ... > > > And last point: this module always creates a XftConfig file > > in /usr/X11R6/lib/X11/, which leads to the behaviour that my X-Server > > uses different fonts than before! I want to keep my settings. > > Uh? How can it use different fonts? Are you sure this is not "Bug 69337: > font installer removes xfs from XF86Config-4 file"? Your right that the > XftConfig file is always created - but what harm can this do? All it will > do is add your X directories to it - and your Xft directories to X. This > way both have the same "view" of installed fonts. What about the sequence ? Can this be a problem ? In the created XftConfig file I have: more /usr/X11R6/lib/X11/XftConfig dir "/usr/local/share/fonts" dir "/usr/share/fonts" dir "/usr/X11R6/lib/X11/fonts" dir "/usr/share/fonts/default" dir "/usr/share/fonts/ja" dir "/usr/share/fonts/NT" dir "/usr/X11R6/lib/X11/fonts/100dpi" dir "/usr/X11R6/lib/X11/fonts/75dpi" dir "/usr/X11R6/lib/X11/fonts/latin2" dir "/usr/X11R6/lib/X11/fonts/local" dir "/usr/X11R6/lib/X11/fonts/misc" dir "/usr/X11R6/lib/X11/fonts/PEX" dir "/usr/X11R6/lib/X11/fonts/Speedo" dir "/usr/X11R6/lib/X11/fonts/TTF" dir "/usr/X11R6/lib/X11/fonts/Type1" In my xfs config file I have: catalogue = /usr/share/fonts/NT, /usr/share/fonts/default/TrueType, /usr/X11R6/lib/X11/fonts/misc, /usr/X11R6/lib/X11/fonts/100dpi, /usr/X11R6/lib/X11/fonts/Type1, /usr/X11R6/lib/X11/fonts/Speedo, /usr/X11R6/lib/X11/fonts/latin2/Type1, /usr/share/fonts/default/Type1, /usr/share/fonts/ja/TrueType, /usr/local/share/fonts, /usr/share/fonts, /usr/X11R6/lib/X11/fonts, /usr/share/fonts/default, /usr/share/fonts/ja, /usr/X11R6/lib/X11/fonts/75dpi, /usr/X11R6/lib/X11/fonts/latin2, /usr/X11R6/lib/X11/fonts/local, /usr/X11R6/lib/X11/fonts/PEX, /usr/X11R6/lib/X11/fonts/TTF Fact is, that everytime I have the XftConfig file I see two problems: 1) The startup of _every_ KDE program last much (!) longer than without it (it needs a lot of CPU during startup) 2) The fonts used are different. If you don't believe, I can send you screenshots ;-)
Subject: Re: font installer eats all my memory > Hmmm ... I thought simply seetings this font on a widget will do the trick > - > no ? Doesn't Qt do the rest for you ? No. Because I read the font files directly, and use FreeType to create the image that is displayed. Qt will only use installed fonts - and I ant the same code for installed, and non-installed fonts. And seeing as most users will use TTF and Type1 fonts, previews of bitmaps weren't a high priority. > I'll do. This would greatly improve this module (from a usability > standpoint). Yup - I know. The idea of a wishlist item is to create a place for others to "vote" for the idea... > It's not what one would expect. Have a look in the file-open dialog with > automatic preview enabled. _Before_ you really open a file, you simply > select it and you already see the preview. That should here be the same. It's > just a preview, no action. OK - I'll look into this - not realted to this bug report tho! But you're right. Might have to wait for KDE3.2.1 - as its not a major issue. > > Not sre what heppened here. What fonts do you have in "default"? Are > there > > any TTF files? Its possible that the ioslave encountered a bad font - > this > > is known to crash FreeType. > > - -rw-r--r-- 1 root root 0 Dez 2 17:03 Fontmap > - -rw-r--r-- 1 root root 2 Dez 2 17:03 fonts.dir > drwxr-xr-x 2 root root 4096 Dez 23 2001 ghostscript > drwxr-xr-x 2 root root 4096 Dez 2 17:03 TrueType > drwxr-xr-x 2 root root 4096 Dez 2 17:03 Type1 > - -rw-r--r-- 1 root root 0 Dez 2 17:03 XftCache ...where is this located? /usr/X11R6/lib/X11/fonts/default? fonts:/default can be either /usr/X11R6/lib/X11/fonts/default, /usr/share/fotns/default, or /usr/local/share/fonts - I try to "merge" the 3 locations into one virtual folder. > Fact is, that everytime I have the XftConfig file I see two problems: > 1) The startup of _every_ KDE program last much (!) longer than without it > (it needs a lot of CPU during startup) ...know XftConfig bug - it reads all fonts at startup. How old is your Xft? You should really upgrade - use XFree86 4.3 with font config (will need a recompile of kfontinst) - its *much* better. > 2) The fonts used are different. > If you don't believe, I can send you screenshots ;-) I beleive you. Are the fonts AA'ed fonts (i.e. accessed through Xft)? Bitmap fonts? Is this a Qt app, Gtk app? etc. Craig.
Subject: Re: font installer eats all my memory On Tuesday 02 December 2003 18:13, you wrote: > No. Because I read the font files directly, and use FreeType to create the > image that is displayed. Qt will only use installed fonts - and I ant the > same code for installed, and non-installed fonts. And seeing as most users > will use TTF and Type1 fonts, previews of bitmaps weren't a high priority. OK. > > > I'll do. This would greatly improve this module (from a usability > > standpoint). > > Yup - I know. The idea of a wishlist item is to create a place for others > to "vote" for the idea... I know, thanks. I'll create a new wish. http://bugs.kde.org/show_bug.cgi?id=69513 > > > It's not what one would expect. Have a look in the file-open dialog with > > automatic preview enabled. _Before_ you really open a file, you simply > > select it and you already see the preview. That should here be the same. > > It's > > > just a preview, no action. > > OK - I'll look into this - not realted to this bug report tho! But you're > right. Might have to wait for KDE3.2.1 - as its not a major issue. OK. I'll also create a new wish for it. http://bugs.kde.org/show_bug.cgi?id=69516 > > > > Not sre what heppened here. What fonts do you have in "default"? Are > > > > there > > > > > any TTF files? Its possible that the ioslave encountered a bad font - > > > > this > > > > > is known to crash FreeType. > > > > - -rw-r--r-- 1 root root 0 Dez 2 17:03 Fontmap > > - -rw-r--r-- 1 root root 2 Dez 2 17:03 fonts.dir > > drwxr-xr-x 2 root root 4096 Dez 23 2001 ghostscript > > drwxr-xr-x 2 root root 4096 Dez 2 17:03 TrueType > > drwxr-xr-x 2 root root 4096 Dez 2 17:03 Type1 > > - -rw-r--r-- 1 root root 0 Dez 2 17:03 XftCache > > ...where is this located? /usr/X11R6/lib/X11/fonts/default? fonts:/default > can be either /usr/X11R6/lib/X11/fonts/default, /usr/share/fotns/default, > or /usr/local/share/fonts - I try to "merge" the 3 locations into one > virtual folder. I have only in /usr/share/fonts/default/ > > > Fact is, that everytime I have the XftConfig file I see two problems: > > 1) The startup of _every_ KDE program last much (!) longer than without > > it (it needs a lot of CPU during startup) > > ...know XftConfig bug - it reads all fonts at startup. How old is your Xft? > You should really upgrade - use XFree86 4.3 with font config (will need a > recompile of kfontinst) - its *much* better. I tried this, but the video driver in 4.3.0 did not work with my laptops graphics card - so I stayed in 4.2.0 (And I read that 4.4.0 is about to be released mid december or so ...) > > 2) The fonts used are different. > > If you don't believe, I can send you screenshots ;-) > > I beleive you. Are the fonts AA'ed fonts (i.e. accessed through Xft)? If you mean if I have activated the AA option in KDE - no, I did not. > Bitmap fonts? Is this a Qt app, Gtk app? etc. I see it e.g. when I start a new KDE konsole window. Or any other KDE app. And what font it is ? You mean before or after ? I have defined in kcontrol/Appearance/Fonts for all fonts (except fixed width) to use "Helvetica [Adobe]" With XftConfig it uses some font which looks edgy.
Subject: Re: font installer eats all my memory > > Yup - I know. The idea of a wishlist item is to create a place for > others > > to "vote" for the idea... > > I know, thanks. I'll create a new wish. > http://bugs.kde.org/show_bug.cgi?id=69513 ... > > OK - I'll look into this - not realted to this bug report tho! But > you're > > right. Might have to wait for KDE3.2.1 - as its not a major issue. > > OK. I'll also create a new wish for it. > http://bugs.kde.org/show_bug.cgi?id=69516 Thanks - just what I need more bugs, only joking! ;-) > > I have only in /usr/share/fonts/default/ Hmm.. Ok, just wanted toknow the location. Can't be a bad font then, as there arne't any in the directory... > I see it e.g. when I start a new KDE konsole window. Or any other KDE app. > And what font it is ? You mean before or after ? > I have defined in kcontrol/Appearance/Fonts for all fonts (except fixed > width) > to use "Helvetica [Adobe]" > With XftConfig it uses some font which looks edgy. But is "Helvetica [Adobe]" a bitmap or Type1 font? Use kcmshell fonts, and open the font up, check it at different sizes to see if it scales. Looking at my system, it appears as if this is a bitmap font - therefore, I'd assume the problem is that something is trying to scale the font. What appens when you enable AA - you can set it to exclude a certain range, which is what I have so that konsole is not AA'ed. >
Subject: Re: font installer eats all my memory On Tuesday 02 December 2003 18:45, you wrote: > > > I have only in /usr/share/fonts/default/ > > Hmm.. Ok, just wanted toknow the location. Can't be a bad font then, as > there arne't any in the directory... No, sorry. I meant I only have the "default" directory in the above location. The content is ls /usr/share/fonts/default/ Fontmap fonts.dir ghostscript TrueType Type1 XftCache > > > I see it e.g. when I start a new KDE konsole window. Or any other KDE > > app. And what font it is ? You mean before or after ? > > I have defined in kcontrol/Appearance/Fonts for all fonts (except fixed > > width) > > to use "Helvetica [Adobe]" > > With XftConfig it uses some font which looks edgy. > > But is "Helvetica [Adobe]" a bitmap or Type1 font? Use kcmshell fonts, and > open the font up, check it at different sizes to see if it scales. Looking > at my system, it appears as if this is a bitmap font Yes, it seems to be a bitmap font. > - therefore, I'd > assume the problem is that something is trying to scale the font. No, can't be. The other font look completely different (e.g. look at the digit "0") http://members.aon.at/m.koller/konsole1-good.png http://members.aon.at/m.koller/konsole1-bad.png > What > appens when you enable AA - you can set it to exclude a certain range, > which is what I have so that konsole is not AA'ed. If I open 2 konsole windows, one before kcontrol, one after - why should the fontsize be different ? Who should try to scale ?
Subject: Re: font installer eats all my memory Wow - thats 2 completely different fonts! The thing is I use (under KDE3.2) Helvetica - and it works fine! What does kcmshell fonts show for Helvetica when you open the font selector?
Subject: Re: font installer eats all my memory On Tuesday 02 December 2003 22:03, you wrote: > > Wow - thats 2 completely different fonts! The thing is I use (under KDE3.2) > Helvetica - and it works fine! What does kcmshell fonts show for Helvetica > when you open the font selector? http://members.aon.at/m.koller/fonts.png http://members.aon.at/m.koller/fonts-selector.png
Subject: Re: font installer eats all my memory Well they look "ok", are these before, or after shots? Also, what dpi is X running in? I noticed that you have both 75dpi and 100dpi fonts installed - this *may* be a problem. What dpi is Xft running in? I know Mandrake did (and probably still does), forced Xft to 90dpi, different to X!!! This was set in /etc/X11/Xresources and /etc/X11/xdm/Xresources Do these files on your system have a line such as "Xft.dpi: 90"?
Subject: Re: font installer eats all my memory On Tuesday 02 December 2003 22:53, you wrote: > > Well they look "ok", are these before, or after shots? They are "before", when all works ok. Here are the "after" shots: http://members.aon.at/m.koller/fonts-bad.png http://members.aon.at/m.koller/fonts-selector-bad.png > Also, what dpi is X > running in? resolution: 116x115 dots per inch > I noticed that you have both 75dpi and 100dpi fonts installed - > this *may* be a problem. Yes. But In my original xfs config file, the 75dpi were not mentioned. catalogue = /usr/share/fonts/NT, /usr/share/fonts/default/TrueType, /usr/X11R6/lib/X11/fonts/misc, /usr/X11R6/lib/X11/fonts/100dpi, /usr/X11R6/lib/X11/fonts/Type1, /usr/X11R6/lib/X11/fonts/Speedo, /usr/X11R6/lib/X11/fonts/latin2/Type1, /usr/share/fonts/default/Type1, /usr/share/fonts/ja/TrueType After using kcontrol, they are included. catalogue = /usr/share/fonts/NT, /usr/share/fonts/default/TrueType, /usr/X11R6/lib/X11/fonts/misc, /usr/X11R6/lib/X11/fonts/100dpi, /usr/X11R6/lib/X11/fonts/Type1, /usr/X11R6/lib/X11/fonts/Speedo, /usr/X11R6/lib/X11/fonts/latin2/Type1, /usr/share/fonts/default/Type1, /usr/share/fonts/ja/TrueType, /usr/local/share/fonts, /usr/share/fonts, /usr/X11R6/lib/X11/fonts, /usr/share/fonts/default, /usr/share/fonts/ja, /usr/X11R6/lib/X11/fonts/75dpi, /usr/X11R6/lib/X11/fonts/latin2, /usr/X11R6/lib/X11/fonts/local, /usr/X11R6/lib/X11/fonts/PEX, /usr/X11R6/lib/X11/fonts/TTF Do I have to really _remove_ them to be not used, or is this another bug at recreation of the xfs config file? > What dpi is Xft running in? I know Mandrake did > (and probably still does), forced Xft to 90dpi, different to X!!! This was > set in /etc/X11/Xresources and /etc/X11/xdm/Xresources Do these files on > your system have a line such as "Xft.dpi: 90"? I have only the latter file. [/usr/X11R6](:)# grep -i xft /etc/X11/xdm/Xresources [/usr/X11R6](:)#
Well the 75dpi is being added because it contains fonts! The installer doesn't really check if its a bitmap only folder, or the resolution. Try disabling the folder (you can do this from kcmshell kcmfontinst - should be the big red X icon). Does this help? Does /etc/X11/xdm/Xresources specify an Xft resolution? Out of curiosity, does the x font list get refreshed when you install a font? i.e. type "xlfonts" in a konsole before, and after installing a font - you may have to wait a few seconds for the refresh, as I don't call it imediately after installing a font (so that it is not called 100 times when installnig 100 fonts!)
Subject: Re: font installer eats all my memory On Thursday 04 December 2003 12:17, you wrote: > ------- Additional Comments From Craig.Drummond@gmx.net 2003-12-04 12:17 > ------- Well the 75dpi is being added because it contains fonts! The > installer doesn't really check if its a bitmap only folder, or the > resolution. Try disabling the folder (you can do this from kcmshell > kcmfontinst - should be the big red X icon). Does this help? > > Does /etc/X11/xdm/Xresources specify an Xft resolution? No. > Out of curiosity, does the x font list get refreshed when you install a > font? i.e. type "xlfonts" in a konsole before, and after installing a font > - you may have to wait a few seconds for the refresh, as I don't call it > imediately after installing a font (so that it is not called 100 times when > installnig 100 fonts!) Hmmm ... strange. I downloaded a font Metropol.ttf into /tmp Then I started kcontrol, opened the font installer, selected "add new font", selected the Metropol.ttf file, and clicked OK. The I got a strange error dialog with the following text: "Could not write to /usr/local/share/fonts//ja/TrueType/Metropol.ttf.part" What does this tell me ? Why does it try the "ja" subfolder, why does it have two slashes "//" before that, and why is the file named .part ??? Ah - wait: After starting kcontrol/fontinst it showed the content of fonts:/ja/TrueType OK, that explains something. But what about the .part ? And why can't it write ? I mean, I have no subfolder in /usr/local/share/fonts right now, but shouldn't it create that, if it likes to store it there ? OK, I tried a different folder, e.g. fonts:/TTF/ ... same problem. Is that intentional that I can only add fonts to /usr/local/share/fonts ? If so, it seems simply a bug with regards the subfolders. Next try: I created the TTF subfolder and added the font again. That worked now. Doing an xlsfonts before and after that showed, that the font was added. [/tmp](:)# diff fonts.? 5591a5592 > -misc-metropol 95-medium-r-normal--0-0-0-0-p-0-iso10646-1 - -- Best regards/Sch
Subject: Re: font installer eats all my memory Firts of all, this discussion should be taken away from the error report -as it is not related, this will be my last reply via bugs.kde.org - please reply directly to me (Craig.Drummond@gmx.net)... > Subject: Re: font installer eats all my memory > > On Thursday 04 December 2003 12:17, you wrote: > > ------- Additional Comments From Craig.Drummond@gmx.net 2003-12-04 > 12:17 > > ------- Well the 75dpi is being added because it contains fonts! The > > installer doesn't really check if its a bitmap only folder, or the > > resolution. Try disabling the folder (you can do this from kcmshell > > kcmfontinst - should be the big red X icon). Does this help? Does the above help? Or try disabling the 100dpi folder, etc. > > > > Does /etc/X11/xdm/Xresources specify an Xft resolution? > > No. > > > Out of curiosity, does the x font list get refreshed when you install a > > font? i.e. type "xlfonts" in a konsole before, and after installing a > font > > - you may have to wait a few seconds for the refresh, as I don't call it > > imediately after installing a font (so that it is not called 100 times > when > > installnig 100 fonts!) Did the above work? > > Hmmm ... strange. > I downloaded a font Metropol.ttf into /tmp > Then I started kcontrol, opened the font installer, selected "add new > font", > selected the Metropol.ttf file, and clicked OK. > The I got a strange error dialog with the following text: > > "Could not write to /usr/local/share/fonts//ja/TrueType/Metropol.ttf.part" > > What does this tell me ? > Why does it try the "ja" subfolder, why does it have two slashes "//" Don't worry about the double slashes. The "/usr/local/share/fonts/" part is the default install dir, and then I add the "/ja/TrueType/" bit onto the end - causing the double slash. This will not affect the writing to disk, etc. For example ls ///usr//////local will list the same as ls /usr/local > before > that, and why is the file named .part ??? The .part is to do with allowing resuming of dowloads. Its what konqueror does when you download a big file > > Ah - wait: After starting kcontrol/fontinst it showed the content of > fonts:/ja/TrueType I'm confused :-( Did you try to install a TTF font into "fonts:/" (*no* sub folder), using the KControl module? Or did it show "fonts:/ja/TrueType" in the "Location" field? By your "Ah - wait" above do you mean after *restarting" kcontrol, it has "fonts:/ja/TrueType" where it did *not* before? > OK, that explains something. But what about the .part ? And why can't it > write ? I mean, I have no subfolder in /usr/local/share/fonts right now, > but > shouldn't it create that, if it likes to store it there ? > > OK, I tried a different folder, e.g. fonts:/TTF/ ... same problem. > Is that intentional that I can only add fonts to /usr/local/share/fonts ? Yes - as per FHS user installed fonts should be placed into "/usr/local/share/fonts", but listing "fonts:/" will megerge the contents of "/usr/local/share/fonts", "/usr/share/fonts", and "/usr/X11R6/lib/X11/fonts" into one virtual folder. > If so, it seems simply a bug with regards the subfolders. Looks like it. THe following "should" work (as an example): 1. In Kcontrol, list the contents of fonts:/truetype/test . This probably doesn't exist on your system, but pretent that it *only* exists in /usr/X11R6/lib/X11/fonts 2. Click "add fonts", and select a font 3. Installer should try to put font into "/usr/local/share/fonts/truetype/test" - but "/truetype/test" does not exist in /usr/local/share/fonts, so the installer should first create the folder, and then copy the font. > > Next try: I created the TTF subfolder and added the font again. That > worked > now. OK. So its the automatic creation of folders that is not working. Just had a quick peek at the code - and its *not* checking that the folder exists, or creating it as described above. If you, as a non-root user, had used konqueror and tried using fonts:/System/truetype/test (the example above) then it would have worked. I need to add the missing piece of code. Can you create a new bug report for this? Its a very simple fix, but nicer to reference it as a bug fix... > > Doing an xlsfonts before and after that showed, that the font was added. > [/tmp](:)# diff fonts.? > 5591a5592 > > -misc-metropol 95-medium-r-normal--0-0-0-0-p-0-iso10646-1 Yipee!!!!!! I restart xfs by sending a SIGUSR2 (or SIGUSR1, can't remember), but you;ve now proved it works!!!! Thanks for that! > > - -- > Best regards/Sch
Fixed in CVS HEAD