François ANDRIOT wrote:

http://bugs.trinitydesktop.org/show_bug.cgi?id=93

http://bugs.trinitydesktop.org/show_bug.cgi?id=274

http://bugs.trinitydesktop.org/show_bug.cgi?id=384

http://git.trinitydesktop.org/cgit/tde-packaging/tree/debian/squeeze/kdebase...

It seems this is a common returning problem. In some of the comments I read that it's a KDE4/distribution bug also happening with Gnome, but there aren't any links to upstream filed bugs.

Does anyone have more information on the details of this issue?

Julius

2012/12/9 E. Liddell ejlddll@googlemail.com:

On Sun, 9 Dec 2012 17:00:25 +0400 Fat-Zer fatzer2@gmail.com wrote:

Try filtering KDE4 out of your PATH? kde-sunset accomplishes that with a few lines near the beginning of startkde . . .

you mean to put ${KDEDIR}/bin prior to of /usr/bin? already done....

2012/12/9 François ANDRIOT francois.andriot@free.fr:

Le 09/12/2012 14:00, Fat-Zer a écrit :

I think all distros have the same problem someday. It is usually worked around by adding a "plasma-desktop" script in TDE's path (/opt/trinity/bin)

Brrr... that sounds really ugly...

See:

http://bugs.trinitydesktop.org/show_bug.cgi?id=93

http://bugs.trinitydesktop.org/show_bug.cgi?id=274

http://bugs.trinitydesktop.org/show_bug.cgi?id=384

http://git.trinitydesktop.org/cgit/tde-packaging/tree/debian/squeeze/kdebase...

The $DESKTOP_SESSION shell variable is set in 'startkde' script. I think the current value in 3.5.13.1 is "trinity".

thanks for info, that was helpful

Seems I found a reason of all this: trinity runs autostart files from /usr/share as well as from it's own autorun subdirectory. The nice workaround will be to remove /usr/share/autostart from an autorun path. I haven't found yet there those paths are come from but it should work. Anyway it's not a solution...

IMHO the solution will be to stop using files contaning OnlyShowIn=KDE (it will require small fixes in tdelibs and tdebase) and change all such entries in our desktop files to TDE.

2012/12/9 Darrell Anderson darrella@hushmail.com:

I remember this bug hitting me a long time ago. The problem varied for everybody, but was path and environment variable related. For path issues we did a lot of work on fortifying the startkde/starttde script. For example, when the Trinity version of startkde/starttde is run, $TDEDIR/bin is in the search path before /usr/bin.

those path-related fixes are helpless for me cause they don't place the KDEDIR's before /usr/bin if KDEDIR already in the PATH.

For the environment variables the problem was KDE4 startup scripts in /etc/profile.d being sourced during login as well as the Trinity profile.d scripts.

In gentoo it contains only a few DE-independent scripts, so not a problem for me: $ ls /etc/profile.d bash-completion.sh java-config-2.csh java-config-2.sh

Another problem is KDE4 only uses KDEDIRS and not KDEDIR. One solution then is not to use KDEDIRS in Trinity.

seems I haven't run into it yet.

The R14 branch should not have this problem because of the many XDG related changes (e.g., OnlyShowIn=TDE). Environment variables all have been renamed in R14 too (KDEDIR->TDEDIR, etc.).

seems changes to stop run files with OnlyShowIn=KDE wasn't performed yet. here are lines with such checks: tdelibs/kinit/autostart.cpp:181 tdelibs/kio/kio/kservicegroup.cpp:87

Should I fill a bug to track it/make it fixed sooner?

Also, a fringe wild shot, but try running the migratekde3 script against your profile directory. The script is not part of 3.5.13.1 but probably will be part of 3.5.13.2. The script is in GIT tdebase:

http://git.trinitydesktop.org/cgit/tdebase/tree/migratekde3

One more about this script, have you considered to move this functionality as well as functionality of the r14-xdg-update to kconf_update?

2012/12/10 E. Liddell ejlddll@googlemail.com:

Not quite what I meant, but what I *did* mean may be irrelevant in any case, as I haven't had KDE4 installed in many years and Portage many no longer be neatly placing it off in its own ghetto in /usr/kde/4/ .

yes, it's so. since 4.2 AFAIR...

2012/12/9 Fat-Zer fatzer2@gmail.com:

Seems I found a reason of all this: trinity runs autostart files from /usr/share as well as from it's own autorun subdirectory. The nice workaround will be to remove /usr/share/autostart from an autorun path. I haven't found yet there those paths are come from but it should work. Anyway it's not a solution...

This one will be hard to implement cause those lists are based on prefix list (or something like that I don't know how to call it correct). So I'll just apply a patch according to «my solution» and sed all .desktop files on install.