| Summary: | Enhancement: Side-by-side installation of KDE 3 and KDE 4 | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Wouter Deconinck <wdconinc> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | bugwatch, darrella, jcgigglelady, jon.l.cosby, kb9vqf, rfunk |
| Priority: | P5 | ||
| Version: | 3.5.10 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Wouter Deconinck
2009-01-07 14:25:22 CST
Yes, KDE4 and KDE3 should be interchangeable and run side by side. I have just uploaded a new version of kdebase-kde3 that should divert the remaining files and allow installation of kdebase; however that has not yet been tested. I will leave this bug open and assigned in case you or anyone else runs into any more KDE3/KDE4 conflicts or problems. Parallel installation confirmed working (didn't try to login with KDE4 yet). I installed KDE 3.5 and use it daily (thank you!), then added backports to sources.list to get KDE 4.2. Installing kdebase (4.2) went mostly fine (there was a network-manager conflict that I let go to KDE4), but trying to install kubuntu-desktop (with recommendations) pulled in lots of packages that conflict. It wanted to remove: amarok-common-kde3 amarok-engine-xine-kde3 amarok-engine-yauap-kde3 amarok-kde3 ark-kde3 desktop-effects-kde-kde3 k3b-data-kde3 k3b-kde3 kaddressbook-kde3 kdebase-kde3 kdebase-runtime-data-common-kde3 kdepim-kio-plugins-kde3 kdepim-kresources-kde3 kdepim-wizards-kde3 klipper-kde3 kmail-kde3 kmailcvt-kde3 kmix-kde3 knotes-kde3 kontact-kde3 korganizer-kde3 ksmserver-kde3 ksnapshot-kde3 ksystemlog-kde3 ktorrent-kde3 kubuntu-desktop-kde3 There are more if I try to install the KDE4 kdepim, which would be essential for me to be able to try KDE4 as a replacement for KDE3: akregator-kde3 kaddressbook-kde3 kdepim-kio-plugins-kde3 kdepim-kresources-kde3 kdepim-wizards-kde3 kmail-kde3 kmailcvt-kde3 knode-kde3 knotes-kde3 kontact-kde3 korganizer-kde3 I did install both kde and kde3 side by side and everything was OK when I used kde3-kdm (or kdm-kde3) as the window manager. This was my eeepc. At some point I got more RAM so I decided to free some space and uninstall kde3. This means I had to change the display manager from kde3 to kde(4-version). For some reason, it did not work and I lost my X-server and since this eeepc was my only machine I reinstalled it. Could you try and uninstalling kde3 and see if jaunty can successfully revert back to kde(4) Many thanks - kde3 worked brilliantly in my 512mb RAM eeepc. I've installed KDE 3.5 and KDE 4 side-by-side and everything seems to work great for the most part. However, I can't seem to get a network manager for KDE 4. It seems that the KDE3.5 installation removed knetworkmanager in favor of knetworkmanager-kde3, which seems sensible, but I can't use the kde3 version under v. 4. If I try to install either knetworkmanager or wicd in KDE 4, it wants to remove knetworkmanager-kde3. Is there a way to get KDE 3.5 and KDE 4's network managers to coexist peacefully? Is this request still valid or can we close? We have done significant work in the past several releases to ensure Trinity and KDE4 coexist peacefully. Add the recent XDG and menu updates, along with continual conflict reduction efforts, and there should be no problems with using one desktop or the other. Can we close this report as resolved? (In reply to comment #7) > Can we close this report as resolved? I think so, as new TDE programs can even use core KDE libraries as needed. That alone speaks volumes of how far TDE has come in the interoperability realm. ;-) |