Created attachment 65414 [details] Screenshot showing 4.7.3 loading plasma panel and kde3 kicker panel on start Version: unspecified (using KDE 4.7.3) OS: Linux Guys, This bug has plagued kde4 for some time. I am trying to test kde 4.7.3-1, but I cannot get it to load without also loading the kde3 kicker in the middle of the page. This is on Arch Linux which basically just packages a clean upstream kde4 from you guys, so this has got to be a generic kde4 issue. I know openSuSE does something to prevent the conflict, but how do I stop this behavior on Arch? Prior to launching 4.7.3-1, I removed all prior ~/.kde4 directories and the only other existing .kde3 dir is ~/.kdemod3. Why does 4.7.3 insist on loading the kde3 kicker? Look at the attached screenshot. This is what I see when kde4 loads -- that should not happen. Granted the screenshot is wide due to my dual-monitor layout, but this occurs on single monitor setups as well. I don't even know what else to send you that would help. (let me know). I've looked through /usr/share/config/kdm/kdmrc and I can't find anything that would trigger a kicker load. Where to look? On Arch (as in most distros) the old kde is installed in /opt/kde while the new 4.7.3 is installed in /usr/bin, so there shouldn't be a conflict. Regardless, I need to know how to fix this problem so that this conflict doesn't occur with Trinity as well. Let me know what else to send. Thanks. Reproducible: Didn't try Steps to Reproduce: launch kde4 on arch with an earlier kde3 (or Trinity) installed. Actual Results: Plasma panel loads on the bottom and kde3 kicker loads just above the plasma panel Expected Results: No kde3 kicker at all
I think it might be just a misconfiguration of some sort. Btw. does plasma actually crash or did you set "crash" by mistake? ;)
I once met such problem in archlinux after installing kde3mod, but the strange thing is it only happened to one user account. I forgot how the problem got resolved :( And I agree this looks more like packaging or configuration problem. However, I think the same problem has already been reported by the reporter in bug 262444.
Ok, I'll mark it as a duplicate of 262444 then so it can be solved at one place ;) Thanks. *** This bug has been marked as a duplicate of bug 262444 ***