2 Oct
2024
2 Oct
'24
8:41 a.m.
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:
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.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
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.