What did you have to do to get KDE back on your machine? I was pretty upset at how SuSE did these packages myself. The packages off of kde.org did not have any of these quarks. Only issue I had with them were fairly minor in the lack of full SuSE menus. But to uninstall my previous kde2 packages and as seems to be the case on this laptop the init.d startup script for kde, is uncalled for IMO. And to the wholier than thou people out there talking about not installing core software on production machines and blah blah blah......I did say this was a LAPTOP. Not a server by any stretch. Get off your high horse and if you don't have something productive to contribute to a thread why not just say it out loud and save everyone else the bandwidth....... On Sunday 14 April 2002 04:39 am, Tim van Venrooij wrote:
Hi,
FYI, when you install the SuSE KDE3 packages, the KDE2 packages kdebase and kdelibs are removed. That's the reason why kdm does not work any longer. Also the startkde script seems somewhat screwed up: it uses variables KDEHOME and kdehome, the latter uninitialized. Furthermore, it does not refer to ~/.kde3 by default as stated in the comment but to ~/.kde instead. It does not start via a login shell either. Another thing is that the latest SuSE KDE3 rpms do not contain any descriptions.
To my opinion, this sort of issues should have long been resolved before moving the KDE3 packages from the experimental to the normal directories. Considering that at the same time the stable KDE2 core packages were removed from these directories... Bad move SuSE, shame on you.
OK, in the end I got it working, KDE2 and KDE3 together, but it took quite some tweaking and patching.
Regards, Tim