Re: xfs-xtt stopped on upgrade, XF86_S3 at 50-70% CPU

[Taketoshi Sano <kgh12351@nifty.ne.jp>]

Hi.

In <87ya9qabrr.fsf@bittersweet.intra>,
 at "15 Jan 2000 20:19:52 -0800",
 with "xfs-xtt stopped on upgrade, XF86_S3 at 50-70% CPU",
  karlheg@bittersweet.inetarena.com (Karl M. Hegbloom) writes:

>  When `xfs-xtt' got upgraded just now, it stopped the font server.
>  Now the server is running at 50-70% CPU.  I cannot launch any new
>  programs.  When I tried to start a `gnome-terminal' from an XEmacs
>  shell buffer, it just sat there waiting, and the X server went to
>  even higher CPU usage.  I guess it's looping or something trying to
>  access the font server.
> 
>  I restarted the font server, (xfs-xtt) and that didn't help; then I
>  also ran `xset fp rehash', and that did not help either.
> 
>  Either the server needs to re-open the connection to the font server,
>  or the font server should not be stopped and restarted until after it
>  is configured...
> 
>  Though I have a feeling that stopping and restarting it would blow
>  away the X server's connection to it anyway, so the X server still
>  needs to reopen the connection.
> 
>  Who should I report the bug to and against what package, or will you
>  take this as the bug report and file it where it belongs? (TIA)

Today, I happenly found the work-around for this problem.

Try the steps below after stopping/restarting the xfs-xtt:

 1) xset -fp <font path for xfs>
     (if you use unix socket, then "xset -fp 'unix/:7100'")

 2) xset fp default

It seems that Xserver can re-open the connection to the font server
using these steps on my system.

I don't know how we can use this information to fix the bugs, 
but I think this will help some users to work-around this problem.

Regards.
-- 
  Taketoshi Sano: <sano@debian.org>,<sano@debian.or.jp>,<kgh12351@nifty.ne.jp>