Bug 249539

Summary:	install of kde4 hardcodes PATH in profile.env to always prefer 4.1 binaries
Product:	Gentoo Linux	Reporter:	Markus Wernig <public>
Component:	[OLD] Core system	Assignee:	Gentoo KDE team <kde>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Markus Wernig 2008-12-01 22:09:41 UTC

Hi

After unmerging all kde packages, emerging kde-meta:4.1, then emerging kde-meta:3.5, /etc/profile.env has the following:
...
export PATH='/opt/bin:/usr/i486-pc-linux-gnu/gcc-bin/4.1.2:/usr/i686-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin:/usr/kde/4.1/bin:/usr/kde/3.5/bin:/usr/qt/3/bin:/usr/kde/3.4/bin:/usr/games/bin

This breaks the functionality of any other KDE session than 4.1 (which unfortunately is far from stable on my system and thus not usable yet), since the wrong apps, helpers etc. get started.

Reproducible: Always

Steps to Reproduce:
1. unmerge all of KDE
2. emerge kde-meta:4.1
3. emerge kde-meta:3.5
4. Start a kde-3.5 session from the KDM login screen

Actual Results:  
3.5 session has only basic functionality, menu, control center, most configurtion dialogs etc. do not appear at all or display "Empty Page" (sic).

Expected Results:  
All apps working as before

Proposed fix:
Either in profile.env or before, determine whether we are being called during a kde session login and set paths accordingly.
eg something along the lines of:
--- BEGIN SUGGESTION ---
...
PATH="/what/ever:/it/is"
KDEVER=`ps xa | grep startkde | grep -v grep | sed -e s%.*/usr/kde/%% | cut -d / -f1`
[ -n $KDEVER ] && PATH="$PATH:/usr/kde/$KDEVER/bin"
...
--- END SUGGESTION ---

Comment 1 Theo Chatzimichos (RETIRED) archtester

2009-06-06 00:03:55 UTC

after various modifications in eclasses and such, this should be fixed, please reopen if you still encounter this. thanks