QT3 - rebuild gives DCOP issues
Hey all, SuSE 7.3 Pro, KDE 3.0.2 As mentioned on the list earlier, the QT3 RPM for 7.3 (and earlier) for KDE 3.0.2 is set up so Xft is not used (thus preventing anti-aliasing on the desktop and other places). I tried rebuilding the RPM and changing the build.sh script so it included Xft support. But the rebuilt RPM gives the problem where X starts and stops several times then goes into console mode. Very much like the problem many had with KDE 3.0.0. Maybe I rebuilt wrong? This was my first ever attempt to use a source RPM to rebuild a package. Here's the steps I took: 1- Installed the qt3 src RPM from kde.org's SuSE 7.3 release. 2- In SU mode, changed the build.sh script: [ "$VERSION" -lt 800 ] && XFT="-no-xft -no-xrender " || XFT="-xft -xrender -I/usr/include/freetype2/ " changed to [ "$VERSION" -lt 702 ] && XFT="-no-xft -no-xrender " || XFT="-xft -xrender -I/usr/include/freetype2/ " I could see that this worked during the compile. 3- In qt3.spec, changed a statement so: echo "useXft=true" >> ${RPM_BUILD_ROOT}/etc/X11/qtrc rather than useXft=false. 4- Rebuilt using "rpm -bb qt3.spec" . Three i386 RPMs were made with this (qt3, qt3-devel, qt3-devel-doc) I then uninstalled the qt3 RPM that came with 3.0.2, and intalled the newly rebuilt one. But then X wouldn't start. Going back to the "official" RPM fixed that. Since the 8.0 version isn't affected by this Xft issue, I tried the RPM for it as well, but no X start for it either. The problem that caused Adrian to build this without Xft support was in the 4.1 version of X. I'm using 4.2, and had no problem with earlier QT builds (prior to the end of May) that had Xft support. Maybe I missed something? Do I need to rebuild any other RPMs? Why am I as a XFree86 4.2 user being put through this just to get anti-aliasing to work? Why are we given no options? (Frustration questions...) Ah, well. For now, my Star Trek desktop font looks like a big unreadable mess... Later, Joe "Flame" Sullivan -------------------------------------------------------------------------------------- Firechild Web Design and CGI Scripting Services http://firechild.net Secretary, World Association of Internet Marketing http://waim.org Webmaster, Amerikanska - For Americans In Sweden http://amerikanska.com Meta-editor, Open Directory Project http://dmoz.org ---------------------------------------------------------------------------------------
On Thursday 04 July 2002 14.45, Joe Sullivan wrote:
Maybe I missed something? Do I need to rebuild any other RPMs?
I suspect you're seeing a c++ problem here. Unlike C, the symbol table of a c++ library isn't particularly stable, so usually when you recompile it you have to recompile everything that uses it too. I could be wrong of course. If you look at the errors you get when you try startx you should see a lot of symbol lookup failures if I'm right. //Anders
On Thursday 04 July 2002 15.14, Anders Johansson wrote:
I could be wrong of course. If you look at the errors you get when you try startx you should see a lot of symbol lookup failures if I'm right.
The errors I get when attempting to use the rebuilt RPM, the 8.0 RPM, or even a QT3 RPM that was released with KDE 3.0.1 for 7.3 are: DCOPServer up and running. DCOP aborting call from 'anonymous-2182' to 'kded' DCOP aborting call from 'anonymous-2186' to 'knotify' kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. KLauncher: Exiting on signal 1 This is why I said it gives DCOP issues. I remember these same errors from back when KDE 3.0.0 was released (a lot of people had this problem with that release). Using the actual QT3 RPM released with KDE 3.0.2 for 7.3 doesn't do this... just gives me a nasty desktop without anti-aliasing. Using a Star Trek font on the desktop itself, and Arial in the menu just looks horrible without anti-aliasing. Later, Joe "Flame" Sullivan -------------------------------------------------------------------------------------- Firechild Web Design and CGI Scripting Services http://firechild.net Secretary, World Association of Internet Marketing http://waim.org Webmaster, Amerikanska - For Americans In Sweden http://amerikanska.com Meta-editor, Open Directory Project http://dmoz.org ---------------------------------------------------------------------------------------
* Joe Sullivan (firechild@telia.com) [020704 05:59]: :: ::The problem that caused Adrian to build this without Xft support was in the ::4.1 version of X. I'm using 4.2, and had no problem with earlier QT builds ::(prior to the end of May) that had Xft support. :: ::Maybe I missed something? Do I need to rebuild any other RPMs? :: ::Why am I as a XFree86 4.2 user being put through this just to get ::anti-aliasing to work? Why are we given no options? (Frustration ::questions...) :: We could always get together and ask Adrian to build complete pkgs for those of us who have updated to 4.2 as anyone should. :) To hobble 50% of the population because the other 1/2 can't figure out 4.2 fixes bugs in 4.1 is beyond me. I'm still wondering if this wasn't a 2.3.2 bug w/ 2.2.X. I would think they would have fixed 3.0.4 and why would KDE3.0.2 w/ 3.0.4 be messed up yet 3.0.1 w/ 3.0.4 not be? That's my question of the day. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
* Ben Rosenberg
::The problem that caused Adrian to build this without Xft support was in the ::4.1 version of X. I'm using 4.2, and had no problem with earlier QT builds ::(prior to the end of May) that had Xft support.
What was built without Xft support ? BAsed on what I saw, all that happens is that /etc/X11/qtrc as now UseXft set to False iso True. I changed it back to True, and it looks like I still have Antialiasing ?
::Maybe I missed something? Do I need to rebuild any other RPMs?
::Why am I as a XFree86 4.2 user being put through this just to get ::anti-aliasing to work? Why are we given no options? (Frustration ::questions...)
We could always get together and ask Adrian to build complete pkgs for those of us who have updated to 4.2 as anyone should. :)
I would really like to see KDE (3.0.2) rebuilt with - 686 optimization - XF4.2 support - Xft support &c &c &c. I'd love to build them myself from source , but I have no idea how to do that in such a way that my resulting rpms are usable for other (suse 7.3) users. Currently listening to: Roger Waters - NY 26aug87 Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Some say the end is near. =`\<, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
On Thursday 04 July 2002 22.10, Gerhard den Hollander wrote:
What was built without Xft support ?
The QT3 RPM for 7.3.
BAsed on what I saw, all that happens is that /etc/X11/qtrc as now UseXft set to False iso True.
Just tried it. Full restart of the system. Anti-aliasing is on in the control center for KDE and KDM, but I'm still not seeing it for either.
I changed it back to True, and it looks like I still have Antialiasing ?
If you've got anti-aliasing, you must have done something else. Just changing that false to true (and restarting, and even turning anti-aliasing off and back on in the Control Center for the heck of it) did nothing on this end. Later, Joe "Flame" Sullivan -------------------------------------------------------------------------------------- Firechild Web Design and CGI Scripting Services http://firechild.net Secretary, World Association of Internet Marketing http://waim.org Webmaster, Amerikanska - For Americans In Sweden http://amerikanska.com Meta-editor, Open Directory Project http://dmoz.org ---------------------------------------------------------------------------------------
* Joe Sullivan
On Thursday 04 July 2002 22.10, Gerhard den Hollander wrote:
What was built without Xft support ? The QT3 RPM for 7.3.
Aaargh. Now I understand the confuision. Maybe I did not install the new qt then. Currently listening to: rw1984-06-16d1t03 Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Some say the end is near. =`\<, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
participants (4)
-
Anders Johansson -
Ben Rosenberg -
Gerhard den Hollander -
Joe Sullivan