https://bugzilla.novell.com/show_bug.cgi?id=853225 https://bugzilla.novell.com/show_bug.cgi?id=853225#c0 Summary: fc-cache run twice for "noarch" data for 32+64 bit; happens running editor & too often Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse@tlinx.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 When I add a font from "noarch", the install process takes a VERY long time building cache files. Not only does it do this for each font file installed (vs. once at end), but it does it *TWICE* -- fc-cache fc-cache32. It is a "no arch" package. There should be nothing that is 32-or 64 bit dependent in the package. So why is it creating 2 different caches (or maybe they are the same) by 2 different cache programs -- each taking 4-6 minutes/font? IT's also the case that if anything touches a timestamp in /usr/share/fonts, then it regens the caches when starting an editor like gvim. Having a 10 minute delay starting up the editor -- 2 or more times/font is too long. If you start gvim as a normal user -- it runs the font-cache as a normal user and since it can't store it in the system cache dir, it has to be run again when root tries running gvim. Tried running root gvim first, but still generated user wait (~1.5 minutes if root done first?)... Reproducible: Always Steps to Reproduce: 1. 2. If any changes are made in font dir, it also regenerates when you start vim as NON-ROOT user (i.e. results are tossed -- can't be stored). 3. Actual Results: Install a bunch of fonts... # find /usr/share/fonts -iname "*.[OTot][tT][FCfc]" |wc -l 21178 touch /usr/share/fonts/truetype Try to run 'gvim'... OR install a font (rpm)... notice it runs fc-cache and fc-cache32 to process the addition on a 64-bit machine. Why does it run fc-cache32 at all?? It's supposed to be arch independent. Expected Results: long wait >4 minutes 1) returned immediate and schedule cache to be built in background 2) only call fc-cache -- not both. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.