Summary: | Installing kde-4.1.2 breaks kde-3.5.10 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Graham Murray <graham> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 1i5t5.duncan, esigra, juantxorena, kh_an, pavel.bazika, simon |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 245954 |
Description
Graham Murray
2008-10-11 10:50:23 UTC
What version of kdelibs and kdebase-startkde for kde3 you have? (In reply to comment #1) > What version of kdelibs and kdebase-startkde for kde3 you have? > kdelibs 3.5.10-r1 kdebase-startkde 3.5.10-r3 (In reply to comment #2) > (In reply to comment #1) > > What version of kdelibs and kdebase-startkde for kde3 you have? > > > > kdelibs 3.5.10-r1 > kdebase-startkde 3.5.10-r3 There's now a new version of each, kdelibs-3.5.10-r2 and kdebase-startkde-3.5.10-r4 in the tree. See if merging them fixes things up. FWIW, I just merged them here and haven't restarted KDE (3.5) yet, so I don't know if it fixes all my problems here. I do however have a somewhat different setup, with a script that switches out a few things depending on what KDE I'm starting, that I created back when I was testing kde-svn some months ago. That may be why I didn't lose my kmenu entirely, tho I did note KDE4 added some stuff to it. That was fine. What wasn't so great was that mimetype associations got screwed up. I lost web links until I fixed them, and clicking a directory I have on the desktop still brings up kde4 dolphin instead of kde3 konqueror. I'll see if the new revisions help after I quit kde (3), run kbuildsycoca, and restart it. Meanwhile I've not done anything with kde4 yet as I've not yet updated my starter script for it. I had some bugs to research/file first, and discovered this one while I was at it. (In reply to comment #3) > There's now a new version of each, kdelibs-3.5.10-r2 and > kdebase-startkde-3.5.10-r4 in the tree. See if merging them fixes things up. Unfortunately, merging those has has no effect. Also Konqueror is missing its navigation icons, kWalletmanager isn't used anymore and kmail lost its receiving settings I am using KDE 3.5.9, in my case I didn't lost anything (yet), but what happens to me is that after installing KDE 4.1.2, when I start a KDE 3.5.9 session, everything starts up correctly (apparently), but right after the 3.5 desktop finishes loading, the 4.1.2 starts to load too, it replaces my desktop, and its bottom panel gets loaded right over the 3.5 one, so I see the KDE 4.1.2 panel and behind it the 3.5 one. I'll be updating to KDE 3.5.10 today, maybe it will change something. Hi, You can try to run "kbuildsycoca --noincremental". It should return your applications to menu. -- Best regards, Andrei. This still happens with kde-4.2? (In reply to comment #8) > This still happens with kde-4.2? > Yes for me, I've just installed nearly everything from 4.2.1 and my KDE 3 control center was empty, open device in new window looked for dolphin, there were no icons on Kmenu and no keyboard switcher. After running kbuildsycoca at first as my working user, then as root, everything is fine now (without KDE 3 restart). Unfortunately I didn't check if running kbuildsycoca helps just after running it as common user, or running as root is needed. (In reply to comment #9) > After running kbuildsycoca... > Unfortunately I didn't check if running kbuildsycoca helps just after running > it as common user, or running as root is needed. That's fairly standard, any time kbuildsycoca4 is run, it'll overwrite the 3.5 version. Thus, it /was/ often necessary to run kbuildsycoca (without the 4 it's the 3.5 version, as a regular user is fine, as root not necessary at least here) to get 3.5 back. However, I noticed it did NOT kill the 3.5 menus when I installed 4.2.1. I installed from 3.5.10 and based on previous experience, had an extra konsole window open to run kbuildsycoca on as necessary, but it was NOT necessary this time. So whatever you devs did with 4.2.1 seemed to work. I didn't lose the sycoca database this time. Pavel says he did. The difference may be that I don't install quite everything. Perhaps a few ebuilds still trigger the sycoca db overwrite, or maybe it was because I merged from a konsole session in KDE3, which got detected (and kbuildsycoca4 not run), while merging from a VT may not have detected the KDE3 variables and thus thought it could run it even tho KDE3 was running in a different VT. this is fixed with the new kde3 eclasses |