On Thursday 03 April 2003 09:50 am, O'Smith wrote:
On Thursday 03 April 2003 05:57 am, Steven T. Hatton wrote:
I have everything related to Gideon, KMail, etc., working with my KDE and QT, but now the one thing that was working is broken. The QT Assistant now displays boxes where the fonts should be. I have a backup install of qt that works. I'm betting if I download the additional QT stuff and compile it, it will work.
At this point what I want to know is what is causing this? There's something about the way SuSE compiled these bits. I used the same RPMs they provide and compiled them here to create a working install of what was broken in their bits. This is weird.
STH
--------------------------
Steven, I want to thank you for your helpful hints about compiling qt3 & kdelibs3 as that solved the problems I am having as well.
Joe Morris was the one who gave me the idea. All I did was look in the SuSE documentation for instructions on how to do it. I couldn't get the automake rpms to build for me, but I didn't (don't) have time to mess with it.
All the bugs that occurred after updating to KDE 3.1.1 from the SuSE rpms have disappeared for me.
I agree with you also, that having to compile from src.rpms seems a bit unnecessary and why is it happening with SuSE's compiles? Hopefully they will figure it out soon as it is really a PITA to do this each time new files appear. I guess we have to blame ourselves somewhat too for wanting to stay on the leading edge! ;o)
I believe you misspelled /bleeding/. {;-{)>
Of course, I can't say that it was all bad, because I did get a bonus from all this. The new Kontact program is compiled, installed and working nicely on my machine now too. If you will notice the sig below, I have the latest KMail from CVS running, all compliments of the Kontact install.
Kontact? I probably should know what you're talking about, but I don't. Care to enlighten me?
Patrick
I still haven't rebuilt the other QT stuff, and I'm getting errors from `assistant' associated with the broken fonts. It seems related to the image processing of the glyphs. That's pretty much what I figured when I discovered that the .so was at the source of the problem. It's very strange that the same configuration built a working QT on my box, but a broken one when I downloaded. It's equally strange that the `assistant' worked with the otherwise broken QT, but doesn't work with the 'fixed' QT. I really want to understand this one. Here are the errors: Major opcode: 154 Minor opcode: 5 Resource id: 0x85b3a58 X Error: RenderBadPicture (invalid Picture parameter) 182 Major opcode: 154 Minor opcode: 5 Resource id: 0x85b3a58 X Error: RenderBadPicture (invalid Picture parameter) 182 Major opcode: 154 Minor opcode: 5 Resource id: 0x85b3a58 X Error: RenderBadPicture (invalid Picture parameter) 182 Major opcode: 154 Minor opcode: 5 Resource id: 0x85b3a58 X Error: RenderBadPicture (invalid Picture parameter) 182 Major opcode: 154 Minor opcode: 5 Resource id: 0x85b3a58 X Error: RenderBadPicture (invalid Picture parameter) 182 Major opcode: 154 Minor opcode: 5 Resource id: 0x85b3a58