[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Every app in 2.1.1 crashes (using antialiasing)
From:       Melchior FRANZ <a8603365 () unet ! univie ! ac ! at>
Date:       2001-04-04 12:09:43
[Download RAW message or body]

* Lars Knoll -- Wednesday 04 April 2001 12:50:
> * On Wednesday 04 April 2001 12:35, Melchior FRANZ wrote:
> > * Lars Knoll -- Wednesday 04 April 2001 10:45:
> > > Did you try if AAed xterm xrashes?
> >
> > No. How can I activate AA in xterm? The manpage says nothing about it.
> > And "$ QT_XFT=1 xterm"  would probably refuse to work.
> > ?
> Try 'xterm -fa courier-10'

Hmm ... my xterm understands -fa, but neither "man xterm" nor "xterm -h"
seem to know that. But, anyway, I tried it:

I introduced a buggy directory path in XftConfig:

-  dir "/usr/X11R6/lib/X11/fonts/truetype"
+  dir "/usr/X11R6/lib/X11/fonts/truetype~"


... and tried:

  $ xterm                      # works (of course without AA)
  $ xterm -fa courier-10       # works (of course without AA, because
                               # the path in XftConfig is wrong. :-)
  $ QT_XFT=0 designer          # works
  $ QT_XFT=1 designer          # segfault!


However, when I last tried to find the bug (a month ago) I got:

  Program received signal SIGSEGV, Segmentation fault.
   0x406c6244 in XmbTextExtents () from /usr/X11R6/lib/libX11.so.6

so, actually libX11 is segfaulting. But, could it be, that Qt ignores a
return value, through which XFree is trying to tell, that Xft won't
work correctly? The only occurrence of XmbTextExtents in Qt is in
"qfont_x11.cpp". Hmmm ...

m.
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]