Le Mon, 14 Nov 2011 05:10:44 -0800 (PST), Darrell Anderson <humanreadable@...> a �crit : > > If you use the kdeetc3-3.5.13-noarch-1.tgz package I > > already sent to > > the list, there is the /etc/profile.d/kde3.sh script which > > sets the > > KDEDIR (without the 'S') variable to /opt/kde3 (just adapt > > it > > to your actual Trinity installation prefix). > > You can then prevent Plasma from loading by > > $ unset KDEDIRS > > before running /opt/kde3/bin/startkde: it is set by the > > KDE4 Slackware > > packages in /etc/profile.d/kde.sh. Trinity will then use > > the KDEDIR > > variable that is set, in my case, to /opt/kde3. > > (in fact if you keep this KDEDIRS variable you will also > > have other > > issues, such as broken Konqueror home page and half-broken > > translations because the KDE4 ones will be used) > > But the KDE4 autostart files (and then, kmix and akonadi) > > in /usr/share/autostart will still load, it's a known > > problem. > > As a final note, the /etc/profile.d/kde.sh script will not > > break KDE4 > > since KDEDIRS has precedence over KDEDIR. > > I understand what you are explaining. > > Background: I already had disabled the Slackware kde.sh (KDE4) > script. I was starting X from run level 3 and before starting X with > startx I confirmed KDEDIRS was not set. The problem is the way the > Trinity startkde script is written. That environment variable is > supposed to be user defined and not globally defined. The Trinity > startkde script adds /usr to the KDEDIRS path, which causes the KDE 4 > problems. > > I have been using KDEDIRS with 3.5.10 for several years to store > local changes I prefer that always take precedence over any upstream > changes from KDE or Slackware. Now that the Trinity startkde script > is modifying that variable I don't know what other effects that will > have. > > If having the Trinity startkde script set KDEDIRS is a hack to create > a compatible environment with KDE 4, then I think this is the wrong > approach. With that said, I will modify the Trinity startkde script > one way or another. Unsetting KDEDIRS is wrong because if end users > want to define that variable the Trinity startkde script will be > negating any such effort. I did this in my .xinitrc (I launch X manually) so the unsetting of KDEDIRS was local in my case. > > I stopped having problems with KDE 4 apps starting after I deleted > the startkde code setting KDEDIRS. Do the KDE4 kmix and akonadi still start on Trinity launch ? The startkde code never set KDEDIRS for me since I use the /opt/kde3 prefix, and the /usr/share/autostart files are still interpreted by Trinity. > > Darrell > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > trinity-devel-unsubscribe@... For additional > commands, e-mail: trinity-devel-help@... Read > list messsages on the Web archive: > http://trinity-devel.pearsoncomputing.net/ Please remember not to > top-post: > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting >