kde problems in hoary after upgrade

[Zach]

Sigh, reboot after reboot hasn't seemed to fix anything.  For me xorg
starts fine.  It even runs fluxbox fine.  Just seems that anytime you
load up the qt libraries (either KDE directly or a KDE app), the
system locks up.

Unless anybody else knows what's going on, I guess I just hope an
apt-get dist-upgrade tonight clears things up.
Barring that, perhaps a dpkg-reconfigure [whaterver-xorg-package-is]
might clear things up.

Open to any & all suggstions.

Thanks

> Date: Fri, 1 Apr 2005 07:52:43 -0500
> From: Zach <uid000 at gmail.com>
> Subject: kde problems in hoary after upgrade
> To: ubuntu-users at lists.ubuntu.com
> Message-ID: <fb4429d10504010452409f5aa9 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Anybody have problems with KDE in hoary after dist-upgrade last night?
>  After upgrading, when I log in, KDE get's to it's splash screen and
> freezes.  I was working on my mythtv, so I installed fluxbox to allow
> me to continue working while waiting for the apt-gods to fix the
> problem.  When I start mythfrontend, the same problem happens--starts
> to load and freezes.  Myth relies on KDE libraries, so this is
> probably the same problem.
> 
> Anyway, I can still ssh to the box and top reveals that x.org is using
> 99% cpu.  /var/log/messages doesn't show anything useful, nor does
> dmesg.
> 
> Just checked this morning and after all night, Xorg is still using 99%
> cpu.  Not at home right now, so I can't see if KDE ever loaded.
> 
> System details
> (K)ubuntu
> Athlon XP cpu
> `uname -r` = 2.6.10-5-k7
> 
> Anybody else? Is this a known bug? Any suggestions?
> 
> Thanks
> Zach
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 1 Apr 2005 08:43:51 -0500
> From: kleeman <ulist at gs1.ubuntuforums.org>
> Subject: Re: kde problems in hoary after upgrade
> To: ubuntu-users at lists.ubuntu.com
> Message-ID: <kleeman.1mtb8y at gs1.ubuntuforums.org>
> 
> I had a problem with xorg last night after the upgrade as restricted
> modules was upgraded and the nvidia module didn't match the kernel so X
> refused to restart. A reboot fixed things.
> 
> --
> kleeman
>