On Wed, Oct 2, 2024 at 10:41 (+0200), Dr. Nikolaus Klepp via tde-users wrote:
> Anno domini 2024 Wed, 2 Oct 02:53:39 -0500
> David C. Rankin via tde-users scripsit:
>> On 10/1/24 7:16 PM, bonkmaykr via tde-users wrote:
>>> I have actually had problems getting some Trinity applications to run
>>> under Windowmaker. Setting TDE path did not seem to help much.
>>> Amarok 1.4 simply crashes with an std::out along the lines telling me to
>>> start amarokapp instead (which doesn't give me a GUI). I installed
>>> Clementine in the mean time.
>>> Other apps work, but they can't read some variables or TDE configuration
>>> properly. So for example Konquerer has no way to remember what file
>>> associations I have set. If I set new ones, it forgets them instantly.
>>> It needs to be told what command to run every time a file is opened.
>>> What could cause this?
>> Windowmaker, and some other traditional X desktops don't do much X-setup. Now
>> invoking konqueror load enough of the TDE environment so it knows where
>> ~/.tde/share/ (or the system-wide files) are located so you have normal
>> file-association, etc. when launching konqueror and when saving any new
>> configurations.
>> This may very well be in the build of tdelibs or tdebase where not everything
>> is made a dependency so this environment is setup when any TDE app is
>> launched. I haven't built TDE on Arch since the 13.5-sru / pre-14 days, so I'm
>> a bit behind on this.
>> As a good diagnosis, launch the TDE app (e.g. konqueror) from the command-line
>> in an x-term and see what additional error/diagnostic messages are written to
>> the terminal (and possibly ~/.xsession-errors -- if launching X redirects
>> errors to that file)
>> This is one that will just need tracking down.
> When I use FVWM I have to do this stuff to get TDE applications working (it's in my .xinitrc):
> export TDE_FULL_SESSION=false
> export TDEHOME=$HOME/.trinity
> export TDEROOTHOME=/root/.trinity
> export TDE_SESSION_UID=$UID
> export TDE_MULTIHEAD=false
> export TDEDIR=/opt/trinity
> export XDG_CONFIG_DIRS=/opt/trinity/etc/xdg
> eport XDG_DATA_DIRS=/opt/trinity/share:/usr/local/share:/usr/share
> tdeinit_shutdown
> tdeinit
> #terminator --geometry=800x500-0-0 &
> fvwm >/tmp/fvwm.log 2>&1
> tdeinit_shutdown
> If I don't, then TDE applications show interestin behaviour like tcontrol with empty tree etc.
?
I use fvwm3 (but up until recently used fvwm2). I explicity put
/opt/trinity/bin in PATH, but other than that, everything *I* have in my
environment is automagically picked up when my X session starts.
But I don't have TDE_FULL_SESSION, TDEHOME, TDEROOTHOME, TDE_SESSION_UID,
or TDE_MULTIHEAD. I have trinity in both of those XDG variables, although
I have other entried in XDG_CONFIG_DIRS as well.
I don't explicitly start up tdeinit.
Having said all that, while I don't use a lot of TDE programs, I do use a
number of them (korganizer+korgac all the time, ksnapshot frequently, and
others more sporadically) and I don't run into any problems. Given that
the TDE programs I use run OK without them (except for the occasional
glitch in korganizer), I am curious about your comments above. Do you care
to go into any more detail about what goes wrong if you don't have those
things in your ~/.xinitrc ?
Cheers.
Jim
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
