Still Desperate: KDE 2.1.1 Won't Work
I've tried deleting /tmp/* (going even further than Crazy Diamond), I've removed all of the KDE 2.1 RPM's (per others' intructions), I've even edited the XftConfig file to insure that it wasn't some how misconfigured (causing some critical fonts not to be there). Nothing. That's right, Nothing has improved the situation. After redownloading KDE 2.1.1 for the 3rd time, it actually installed in YaST1 without pre-init errors, but alas that doesn't help the fact that after switching on AA, KDE crashes at Kicker startup. Additionally, no matter what I do child panels don't load their applets like they are suppose to on restarting KDE. I'm at a loss. KDE 2.1 works fine (it works even better with Qt 2.3), but KDE 2.1.1 just WON'T WORK! Now, granted KDE 2.1.1 doesn't have many feature improvements, and I don't have any instablity problems, but it bothers me that 2.1.1 is the ONLY, read ONLY, non-CVS version of KDE that hasn't installed for me. Infact pretty much every version (except the 1.9x series of betas) installed and worked within a few minutes. Should I try the KDE2 RPM's on ftp.suse.com? Are they different? Any other ideas? Thanks, Tim -- ----------------------------------------------------------------- Timothy R. Butler Universal Networks ICQ #12495932 AIM: Uninettm Christian Web Services Since 1996 tbutler@uninetsolutions.com http://www.uninetsolutions.com ============== "Information Powered by Innovation" ============== "AT&T: The pre-paid phone card. Jesus: The pre-paid life card."
On Mon, 2 Apr 2001 18:50:07 -0500, Timothy R.Butler wrote:
I've tried deleting /tmp/* (going even further than Crazy Diamond), I've removed all of the KDE 2.1 RPM's (per others' intructions), I've even edited the XftConfig file to insure that it wasn't some how misconfigured (causing some critical fonts not to be there).
Nothing. That's right, Nothing has improved the situation.
After redownloading KDE 2.1.1 for the 3rd time, it actually installed in YaST1 without pre-init errors, but alas that doesn't help the fact that after switching on AA, KDE crashes at Kicker startup. Additionally, no matter what I do child panels don't load their applets like they are suppose to on restarting KDE. I'm at a loss. KDE 2.1 works fine (it works even better with Qt 2.3), but KDE 2.1.1 just WON'T WORK! Now, granted KDE 2.1.1 doesn't have many feature improvements, and I don't have any instablity problems, but it bothers me that 2.1.1 is the ONLY, read ONLY, non-CVS version of KDE that hasn't installed for me. Infact pretty much every version (except the 1.9x series of betas) installed and worked within a few minutes.
Should I try the KDE2 RPM's on ftp.suse.com? Are they different? Any other ideas?
HI Tim, I have/had the same problem that switching on AA on KDE 2.1.1 causes the Kicker crash at startup. I downloaded the files from sourceforge and then tried the files from SuSE and the results were exactly the same Kicker crash. So what I have done is to install KDE 2.1.1 without using KDE to switch on the AA. Installed true type fonts. Ran the following commands: # ttmkfdir -o fonts.dir # SuSEconfig -module fonts This appears to work for me. Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01 +*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ For my public PGP key send email with subject: "Send_PGP_Key" +*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
Hi Ralph,
I have/had the same problem that switching on AA on KDE 2.1.1 causes the Kicker crash at startup. I downloaded the files from sourceforge and then tried the files from SuSE and the results were exactly the same Kicker crash.
So what I have done is to install KDE 2.1.1 without using KDE to switch on the AA. Installed true type fonts. Ran the following commands: # ttmkfdir -o fonts.dir # SuSEconfig -module fonts
Hmm... thanks for the suggestion. Just out of curiousity though, how did you turn AA on if you didn't enable it via the KDE 2.1.1 control panel? Thanks so much! -Tim -- ----------------------------------------------------------------- Timothy R. Butler Universal Networks Information Tech. Consultant Christian Web Services Since 1996 ICQ #12495932 AIM: Uninettm An Authorized IPSwitch Reseller tbutler@uninetsolutions.com http://www.uninetsolutions.com ============== "Information Powered by Innovation" ==============
On Mon, 2 Apr 2001 22:02:15 -0500, Timothy R. Butler wrote:
Hi Ralph,
I have/had the same problem that switching on AA on KDE 2.1.1 causes the Kicker crash at startup. I downloaded the files from sourceforge and then tried the files from SuSE and the results were exactly the same Kicker crash.
So what I have done is to install KDE 2.1.1 without using KDE to switch on the AA. Installed true type fonts. Ran the following commands: # ttmkfdir -o fonts.dir # SuSEconfig -module fonts
Hmm... thanks for the suggestion. Just out of curiousity though, how did you turn AA on if you didn't enable it via the KDE 2.1.1 control panel?
Thanks so much!
-Tim
--
Hi Tim, Using the instructions as previously mentioned by Lenz Grimmer and Nadeen Hasan, the above is what was needed before KDE 2.1 was released. So I just pretended that KDE 2.1.1 does not have an AA switch made the above changes and called it a day. Is it "real" antialiasing? I don't know. The Truetype fonts that I wanted now show up on KDE and StarOffice font lists. Netscape has an oversized 12 pt truetype font for everything. But most importantly my limited testing of importing and exporting documents between MS Office and Star Office is now done using the same fonts and the 72 pt Arial font used for my company letterhead in Star Office is now smooth and somewhat fuzzy as opposed to blocky and jagged. Arial and Times New Roman truetype fonts in Star Office are what I had actually wanted. So I consider anything above that as a bonus. Ralph Sanford - If your government does not trust you, rsanford@telusplanet.net - should you trust your government? DH/DSS Key - 0x7A1BEA01 +*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ For my public PGP key send email with subject: "Send_PGP_Key" +*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
participants (2)
-
Ralph Sanford
-
Timothy R.Butler