[arch-general] kde4 loads kde3 parts -- is this a packaging issue?
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.
On Saturday 26 February 2011 04:50:50 David C. Rankin wrote:
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.
Just a wild guess from someone who spent quite a while trying to get KDE 3.5.n installed in /opt load in an environment with 3.5.m was installed in /usr (where n>m): what is your $KDEDIRS variable? (Note the fact that KDE has used singular and plural of this variable over the years). Additionally, I suppose it might be an XDG thing. Take a look inside some of the .desktop files, e.g. for plasma: /usr/share/autostart/plasma-desktop.desktop: [Desktop Entry] Exec=plasma-desktop X-DBUS-StartupType=wait Name=Plasma Desktop Workspace <snip translations> Type=Service X-KDE-StartupNotify=false OnlyShowIn=KDE; X-KDE-autostart-phase=0 The key here is that something detected that you're in KDE, and hence the OnlyShowIn=KDE kicked in and loaded it. I know much less than other on this list about how these XDG things work, but it seems to me you might need to have some new option for OnlyShowIn for KDE3 or TRINITY or somesuch. Pete.
On 26 February 2011 05:50, David C. Rankin
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
On Sat, 26 Feb 2011 13:17:14 +0100 Lukáš Jirkovský wrote:
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.
There be even directories from kde3/4 in /tmp and in /var/tmp. But starting with runlevel 3 and delete all kde things in both directories could never be wrong. :) See you, Attila
On Fri, 25 Feb 2011 22:50:50 -0600
"David C. Rankin"
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?
The problem might be related to /usr/share/autostart and similar in $HOME being shared by kde4 and kdemod. That is my guess anyway. You could take a look at the paths etc on whatever distro that has both kde4 and kde3 working fine alongside and see what they are doing to them.
participants (5)
-
Attila
-
David C. Rankin
-
Lukáš Jirkovský
-
Peter Lewis
-
Øyvind Heggstad