Re: [suse-kde] Problems with KDE3.0.2

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . Allllrighty then. I had just DLed K3.02 and backed up my 7.3 system, in prep to try 3.0.2 alongside KDE2. But not any more. Thanks Frederico. Does anyone know the status of Suse? On Thursday 08 August 2002 12:05 pm, you wrote:

at Randall's request, i forward his mail to the relevant lists.

As for the comments that my original post generated, I would like to point out that many people failed to realize that I did NOT upgrade to KDE 3.0.2 intentionally. I only installed it beacuse the patches were on YOU and I did an automatic update (which i will never do again, I learned my lesson). That upgrade was supposed to fix bugs and security holes and left me with a very broken system - not a nice surprise.

federico

---------- Forwarded Message ----------

Subject: Problems with KDE3.0.2 Date: Wed, 7 Aug 2002 20:07:09 -0400 From: Randall Wood To: federico.damonte@unipd.it

Hello Federico:

You saved my Linux system. Thanks so much.

I was surfing the SuSE Linux suse-kde mailing list archives on line, and your message about KDE3.02 problems on SuSE were an exact match for the problems I've had with my machine, and I've been tearing my hair out trying to fix them. So thanks for your detailed message with gave me the info I needed to fix my problems: Yast2, kppp, and kinternet.

Do me a favor and help me help the rest of the SuSE community by posting my message to the mailing list, to reaffirm that yes, other people are having the same troubles as you describe.

I visited the SuSE support database daily in search of new articles describing why Yast2 had choked; nothing. I sent in support requests by email; nothing. I tried applying to the mailing list myself but was unable to (which is why I'd appreciate your posting my message on my behalf; I couldn't get subscribed). Nothing I tried found me the answers. I even tried removing and reinstalling the KDE3.0.2 RPMs to see if that would help. Tonight I was planning on reinstalling SuSE 8.0 to get a functioning Yast2; last night I even backed up all the home directories in preparation for tonight's ordeal.

Thanks for the info. Help me help the rest of the group by posting this message, confirming your experience and mine were the same.

I suspect SuSE's in trouble, but I don't know why. Their support lines are unresponsive, their servers seem to be perpetually DOSed, and their latest SDB articles include one about how to send a proper help request email so that their spam filters don't weed it out. I think someone's either DOSing them or something; don't know what, but I agree with you: I can forgive SuSE for putting out bad RPMs, given the immediate demand users have for the latest software. But I resent the lack of communication on SuSE's part. I have no reason to believe they even read my email; I've heard nothing from them.

Best wishes,

Randy Wood

- -- To the systems programmer, users and applications serve only to provide a test load. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj1SrLEACgkQnQ18+PFcZJua1QCfeUCa6J6iIQXw1qstWeaECCuB 6N8AnjnWyaBmqqLCgGbg/nBx8wrMWST2 =KK/4 -----END PGP SIGNATURE-----