On 26 February 2011 05:50, David C. Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> wrote: > Guys, > > I need some help figuring out where to start in trying to keep kde4 from > loading most of kde3 when kde4 is launched from the kdm chooser. A picture is > worth 1000 words: > > [109k] (800x600) > http://www.3111skyline.com/dl/dt/trinity/ss/ArchLinux_kde3+kde4.800.jpg > > (full res 264k 1280x800) > http://www.3111skyline.com/dl/dt/trinity/ss/ArchLinux_kde3+kde4.jpg > > In the screenshot, kde (kde4) was launched from the kde4 kdm. The background > is the kde4 background. Both the kde3 kicker and kde4 plasma-panel loaded (and > are both fully operational) at the bottom of the screen. Launching apps or > system settings the panels, properly loads the corresponding kde3/kde4 app. > > The plasma-desktop has loaded and the kde4 "Desktop Folder is present". The > kde4 window decorations are present, but if you rt-click on the desktop, you get > the kdemod context menus and all kdemod apps are in the default Domino style. > > What I'm trying to do is narrow down why this happens on Arch and so we can > fix it. I'm guessing this probably happens when kde4-kdelibs or kde4-kdebase > gets built and installed, but that is just a guess. > > This seems to be a packaging issue because it doesn't happen with other > distros that have both kde4 and kde3 installed together. It doesn't happen in > reverse either with kdemod3 based on Trinity. Loading the updated kdemod3 > doesn't load the kde4 panel, but kde4 does load the kde3 panel. > > Anybody familiar with this issue on Arch and how it might be solved? > > -- > David C. Rankin, J.D.,P.E. > Just a guess – maybe the cache is shared for both KDE 4 and Trinity and it results in loading the session of both. It should be in /var/tmp, maybe there is something in /tmp too. Lukas
