Bug 115208

Hmm, something for the control center maintainer ? 

Works here...
bug assigned!

(In reply to comment #0)
> Sax2 does not start when invoked from YasT Control Center; after clicking on  
> the Graphics Device settings icon, nothing happens.  

This does not work for me either (Suse 10 RC1 x86_64)
  
> It is however possible to start SaX2 as root from the command line, and it 
> seems to work correctly. The X11 config also works. 

Only from init 3, not from konsole in an open X server.

Marcus, please check the call in the .desktop file! 

I can reproduce this here on my x86_64 machine. Its only on this 
architecture and it seems not to be a sax related problem. The startup is 
that slow because Qt is opening almost all fonts of the system before 
starting up. The next time i call it it is much faster and it opens only 
a few fonts. 
 
I don't know why this is the case but it is not a problem of sax 
Maybe Mike knows more 

I don't think what Marcus observed in comment #5 is related to the
original problem reported.

Why not?:

Marcus found the problem with the slowness on my machine "magellan".

That problem was caused because "SuSEconfig --module fonts" had not
been run recently on "magellan". "SuSEconfig --module fonts" is
important because it calls "fc-cache".

If "fc-cache" has not been run since the last time fonts were
installed or deleted, the system wide cache files "fonts.cache-1" are
not up-to-date. One of theses cache files is in each font
directory. If the system-wide cache files are not up-to-date, a
~/.fonts.cache-1 file is created in the home directory of the user
(which may be "/root" if the applications runs as root).

Creating the personal cache file ~/.fonts.cache-1 can take a long time
if many fonts are installed.  On "magellan", there are *HUGE* amounts
of fonts installed because I need this for testing. On a "normal" SuSE
Linux installation there will not be that many fonts.

But even on default installation of SuSE Linux, the time this takes is
clearly noticeable. It happens with any application using Xft and has
nothing to do with SaX2. "xfd -fa sans" is enough to see this
behavior. Any applications using Xft will create that cache-file.
If that cache-file has been created once, the startup of applications
using Xft will become fast. That is what Marcus observed:

Marcus> The next time i call it it is much faster and it opens only 
Marcus> a few fonts.

If "SuSEconfig --module fonts" is run, fc-cache is called and the
system-wide cache files are updated. The next start of an application
using Xft will then notice that the system-wide cache files are
up-to-date and delete most of the content of the personal cache file
~/.fonts.cache-1.

Application startup will be fast if the system-wide cache files are
up-to-date.

If "SuSEconfig --module fonts" had been run recently on my machine
"magellan", Marcus would not have noticed a problem.

The original bugreport and comment #3 claim that SaX2 doesn't start at
all when started from the control centre. This doesn't sound
like the slowness problem Marcus has observed.

Or does SaX start for you but only slowly?

The slowness problem when the fonts.cache-1 files are out of date has
nothing at all to do neither with SaX2 nor with the way it is started.

By the way, I cannot reproduce the original problem reported either.
SaX2 starts just fine for me from YaST2. Tested on RC2.

Closing as WORKSFORME.