[SOLVED] Font antialiasing of qt3 apps in slack64

veeall · 06-22-2009, 09:20 AM

Hi!
I've installed latest kde3 compatibility packages in my slackware64 installation, got everything working fine exept there is no font antialiasing in qt3 application menus - qtconfig(qt3) or opera for example.
How to turn on font antialiasing of qt3 apps in kde4?

My ~/.fonts.conf contains:

Code:

<?xml version="1.0"?><!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
 <match target="font" >
  <edit mode="assign" name="rgba" >
   <const>none</const>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="hinting" >
   <bool>true</bool>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="hintstyle" >
   <const>hintmedium</const>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="antialias" >
   <bool>true</bool>
  </edit>
 </match>
</fontconfig>

Thanks!

Bruce Hill · 07-09-2009, 03:11 AM

bump ... I'd also like to know, if for nothing else than "xconfig"

stratus · 08-29-2009, 04:01 PM

Hi!

I had the same problem with my Slackware64 Current.

I solved this problem downloading the "compat/qt3.3" source and the slackbuild script from slackware64-current ftp (aka Slackware64 13.0 by now):

ftp://ftp.slackware.no/pub/linux/sla...e3-compat/qt3/

I rebuild the qt3.3 package for my system and got my QT3 fonts with antialiasing!

Good luck

Bruce Hill · 09-01-2009, 05:54 AM

The OP said he already installed ./kde3-compat/ files, and still has no antialiasing.

I've since changed the system (no Qt or KDE on it at all), but before that there was
no antialiasing even with the packages in that directory in ./extra.

Did you rebuild freetype or anything else? Maybe post your SlackBuild for the package(s)?

The one thing I miss from Qt is using "make xconfig" for building custom kernels. That
side-by-side layout and superior search function has me spoiled.

samac · 09-01-2009, 11:05 AM

I just rebuilt the package that stratus mentioned and this worked for me.

samac

veeall · 09-01-2009, 06:02 PM

I haven't checked this solution yet because i'm not currently using any qt3 apps in slack13, but i marked this as SOLVED nevertheless, considering these two success stories posted here.

Thanks, people!

Bruce Hill · 09-01-2009, 06:05 PM

Quote:

Originally Posted by samac

I just rebuilt the package that stratus mentioned and this worked for me.

samac

Why did you rebuild it, and what options were different in your build than the Slackware build?

samac · 09-02-2009, 03:06 AM

Quote:

Why did you rebuild it, and what options were different in your build than the Slackware build?

I made no changes I just ran the script, so I have no idea why it would make a difference, but it does.

samac

Petri Kaukasoina · 09-02-2009, 04:49 AM

Hi,

I can confirm this. The shared library libqt-mt.so.3.3.8 extracted from qt3-3.3.8b-x86_64-opt2.txz does NOT link against libXcursor.so.1, libXft.so.2, libXinerama.so.1, libXrandr.so.2, libXrender.so.1, libexpat.so.1, libfontconfig.so.1, and libfreetype.so.6, while the same library extracted from the 32-bit package qt3-3.3.8b-i486-opt1.txz does.

But a rebuilt package, built from the same Slackbuild on a final Slackware64-13.0, does link to those libraries.

grissiom · 09-02-2009, 06:35 AM

Quote:

Originally Posted by Petri Kaukasoina

Hi,

I can confirm this. The shared library libqt-mt.so.3.3.8 extracted from qt3-3.3.8b-x86_64-opt2.txz does NOT link against libXcursor.so.1, libXft.so.2, libXinerama.so.1, libXrandr.so.2, libXrender.so.1, libexpat.so.1, libfontconfig.so.1, and libfreetype.so.6, while the same library extracted from the 32-bit package qt3-3.3.8b-i486-opt1.txz does.

But a rebuilt package, built from the same Slackbuild on a final Slackware64-13.0, does link to those libraries.

Good seeing~ I think you can mail your discovery to Pat.

dlee99 · 09-03-2009, 04:29 AM

Hi all,

I rebuilt qt3 from the sources as suggested but I still have ugly menufonts in Opera and K3b3
Should I change some other config to enable anti-aliasing?

Is there some way to check if the shared library libqt-mt.so.3.3.8 I used is built against the libs mentioned in Petri's post?

octoberblu3 · 09-03-2009, 10:09 AM

Quote:

Originally Posted by dlee99

Hi all,

I rebuilt qt3 from the sources as suggested but I still have ugly menufonts in Opera and K3b3
Should I change some other config to enable anti-aliasing?

Is there some way to check if the shared library libqt-mt.so.3.3.8 I used is built against the libs mentioned in Petri's post?

try ldd /opt/kde3/lib64/qt3/lib/libqt-mt.so.3.3.8

And just to note, somehow just by running the build script to remake the qt3 package, I checked my old libqt-mt.so.3.3.8 before updating it and now it shows the links to the libraries mentioned above. Now how does that figure?

Petri Kaukasoina · 09-03-2009, 11:42 AM

Quote:

Originally Posted by octoberblu3

And just to note, somehow just by running the build script to remake the qt3 package, I checked my old libqt-mt.so.3.3.8 before updating it and now it shows the links to the libraries mentioned above. Now how does that figure?

qt3.SlackBuild doesn't build the package in some subdirectory of /tmp as usual but in /opt/kde3/lib64/qt3. And it doesn't clean the place afterwards, leaving the source code tree and object files there, too. After building the package, you might want to first removepkg qt3, then rm -rf /opt/kde3/lib64/qt3, and then installpkg the new package again.

octoberblu3 · 09-03-2009, 01:43 PM

Quote:

Originally Posted by Petri Kaukasoina

qt3.SlackBuild doesn't build the package in some subdirectory of /tmp as usual but in /opt/kde3/lib64/qt3. And it doesn't clean the place afterwards, leaving the source code tree and object files there, too. After building the package, you might want to first removepkg qt3, then rm -rf /opt/kde3/lib64/qt3, and then installpkg the new package again.

That would explain it. Thanks. And the rebuild worked great for me. I now have mythtv-0.21 running with everything looking correct as before. Maybe I'll clean up my scripts for myth and submit them to SlackBuilds.

dlee99 · 09-03-2009, 04:54 PM

Quote:

Originally Posted by octoberblu3

try ldd /opt/kde3/lib64/qt3/lib/libqt-mt.so.3.3.8

Well...output gives

Code:

linux-vdso.so.1 =>  (0x00007fff788a0000)
	libmng.so.1 => /usr/lib64/libmng.so.1 (0x00007f9bd3b38000)
	libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x00007f9bd3915000)
	libpng.so.3 => /usr/lib64/libpng.so.3 (0x00007f9bd36d5000)
	libz.so.1 => /usr/lib64/libz.so.1 (0x00007f9bd34c1000)
	libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f9bd323f000)
	libXmu.so.6 => /usr/lib64/libXmu.so.6 (0x00007f9bd3026000)
	libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f9bd2e14000)
	libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f9bd2ada000)
	libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f9bd28d1000)
	libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f9bd26b6000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f9bd24b1000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9bd2295000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f9bd1f8e000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f9bd1d08000)
	libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f9bd1af1000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f9bd1781000)
	liblcms.so.1 => /usr/lib64/liblcms.so.1 (0x00007f9bd1548000)
	libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007f9bd1343000)
	libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f9bd1141000)
	libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f9bd0f3b000)
	libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f9bd0d31000)
	libXt.so.6 => /usr/lib64/libXt.so.6 (0x00007f9bd0ace000)
	libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f9bd08b2000)
	libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f9bd06ad000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f9bd04ab000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f9bd47dc000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f9bd02a2000)
	libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f9bd009f000)

So the libs Petri mentions are missing

Which sources exactly do I have to download to build?