Upgrade to KDE 3.1.2 lock ups
I updated KDE using SuSE's Supllementary RPMS. Now, I have been having problems with Kmail and Konqueror locking up. Is there any way to fix this problem? Do I need to rpm -e --force the base KDE rpms(kdelibs,kdebase,kdenetwork...) and then reinstall them? NeoFax
* NeoFax (neofax@comcast.net) [030527 16:31]: ->I updated KDE using SuSE's Supllementary RPMS. Now, I have been having ->problems with Kmail and Konqueror locking up. Is there any way to fix this ->problem? Do I need to rpm -e --force the base KDE ->rpms(kdelibs,kdebase,kdenetwork...) and then reinstall them? You could try shutting down KDM and then removing all KDE related directories in /tmp then removing .mcop* and the two tmp files in .kde. You then restart KDM and it should be fixed. Sometimes KDE leaves temporary files around and when you upgrade it craps out when accessing them or creating new files. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org The IQ and the life expectancy of the average American recently passed each other going in the opposite direction.
You could try shutting down KDM and then removing all KDE related directories in /tmp then removing .mcop* and the two tmp files in .kde. You then restart KDM and it should be fixed. Sometimes KDE leaves temporary files around and when you upgrade it craps out when >accessing them or creating new files.
I have done this already. Is there any other way of fixing this problem?
* NeoFax (neofax@comcast.net) [030527 19:56]: ->>You could try shutting down KDM and then removing all KDE related ->>directories in /tmp then removing .mcop* and the two tmp files in .kde. ->>You then restart KDM and it should be fixed. Sometimes KDE leaves ->>temporary files around and when you upgrade it craps out when >accessing ->>them or creating new files. -> ->I have done this already. Is there any other way of fixing this problem? You may actually be missing some pkgs. You may not have grabbed everything you need. I use to just download base, app and devel when I was doing it by hand. Now I just count out apt to get what I need ..and it apt usually works quite well unless SuSE does one of their famous pkg switching off apps. But if you have downloaded base, apps and devel an installed each package then something else must be wrong. Anything else changed on the system? -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org The IQ and the life expectancy of the average American recently passed each other going in the opposite direction.
* NeoFax (neofax@comcast.net) [030527 19:56]: ->>You could try shutting down KDM and then removing all KDE related ->>directories in /tmp then removing .mcop* and the two tmp files in .kde. ->>You then restart KDM and it should be fixed. Sometimes KDE leaves ->>temporary files around and when you upgrade it craps out when accessing ->>them or creating new files. -> ->I have done this already. Is there any other way of fixing this
----- Original Message ----- From: "Ben Rosenberg" <ben@whack.org> To: <suse-kde@suse.com> Sent: Tuesday, May 27, 2003 10:02 PM Subject: Re: [suse-kde] Upgrade to KDE 3.1.2 lock ups problem?
You may actually be missing some pkgs. You may not have grabbed everything you need. I use to just download base, app and devel when I was doing it by hand. Now I just count out apt to get what I need ..and it apt usually works quite well unless SuSE does one of their famous pkg switching off apps. But if you have downloaded base, apps and devel an installed each package then something else must be wrong. Anything else changed on the system?
-- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org The IQ and the life expectancy of the average American recently passed each other going in the opposite direction.
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
No, nothing else has changed KDE wise. I also use apt to upgrade the system. Do you know if apt has the orphan program for SuSE. If so, I will just remove kdelibs and then run orphan to see what packages were orphaned and then reinstall. NeoFax
participants (2)
-
Ben Rosenberg -
NeoFax