By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2622 - tqt3 and tqtinterface - /etc/profile.d/tqt3.sh and trinity.sh conflict with other Qt-based DE's
Summary: tqt3 and tqtinterface - /etc/profile.d/tqt3.sh and trinity.sh conflict with o...
Status: NEEDINFO
Alias: None
Product: TDE
Classification: Unclassified
Component: qt3 (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2969
  Show dependency tree / graph
 
Reported: 2016-03-28 20:49 CDT by James
Modified: 2018-08-30 02:24 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James 2016-03-28 20:49:42 CDT 
Arch Linux
tde-tqt3 14.0.3-1
tde-tqtinterface 14.0.3-1

By default, in Arch Linux, bash will "source" files in /etc/profile.d/, and in particular, /etc/profile.d/tqt3.sh and /etc/profile.d/trinity.sh, which contain simply

export QTDIR=/opt/trinity/tqt3
export TQTDIR=/opt/trinity/tqt3
export QT_XFT=true
export PATH+=:/opt/trinity/tqt3/bin
export PKG_CONFIG_PATH+=:/opt/trinity/tqt3/pkgconfig

and

export TDEDIR=/opt/trinity
export TDEDIRS=$TDEDIR
export PATH=$PATH:/usr/bin:$TDEDIR/bin
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:$TDEDIR/lib/pkgconfig
if [ ! -z $XDG_DATA_DIRS ]; then
  export XDG_DATA_DIRS=$XDG_DATA_DIRS:$TDEDIR/share
else
  export XDG_DATA_DIRS=$TDEDIR/share
fi
if [ ! -z $XDG_CONFIG_DIRS ]; then
  export XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$TDEDIR/etc/xdg
else
  export XDG_CONFIG_DIRS=$TDEDIR/etc/xdg
fi


But, when attempting to run some other Qt-based Desktop Environment, such as LXQt or KDE/Plasma5, tqt3.sh and trinity.sh are still "sourced", and redefine the "QT" and "XDG" environment variables with horrible consequences for the alternative DE, which becomes unusable.

One mindless solution would be to wrap those statements with some test,

if ps -C starttde,starttrinity &>/dev/null;then
...
fi

Will that test work when a graphical display manager is being used?  Also, the test should not be confused by some TDE Applet or Application running in the alternate DE, in the same way that a KDE application might be running in GNOME.

Really though, placing these files in /etc/profile.d is very "heavey handed" and not the correct approach.  It seems to me that /opt/trinity/bin/starttde and /opt/trinity/bin/starttrinity should be completely responsible for setting-up the required environment, including any necessary "QT" and "XDG" variables.

Certainly, anyone "playing" with TDE is going to be very upset and unsympathetic if their TDE install unexpectedly makes their LXQt or KDE install unusable!
Comment 1 Slávek Banko 2016-03-29 02:09:41 CDT 
I believe that these files are not included in the source code == apparently are created specifically for Arch Linux. I suppose that such settings should be in build scripts and not installed for users.

Please, you can check the build scripts for Arch Linux and verify where these files originate?
Comment 2 James 2016-03-29 11:59:44 CDT 
Yes, thanks.  I'm sorry, my mistake.  I did not check.  The file tqt3.sh is "hard coded" in the PKGBUILD, and the file trinity.sh is an added file.

There is currently an effort to resurrect and revise some old Arch PKGBUILD files for the TDE, which is not otherwise currently available on Arch.  I don't actually know where they came from, or if there is a version control history available.

So instead, I would ask, do these files appear to be obsolete?  Can I assume that the standard "starttde" file should be all that is needed to properly configure and start the TDE?

Of course, these profile.d files are causing a problem, and I would just as soon delete them if they are not necessary.
Comment 3 James 2016-03-29 23:47:45 CDT 
Hmm - looking at the PKGBUILD files again, I think maybe these environment files are only supposed to be used for the build environment, for tdebindings for instance, and they should not have been placed into /etc/profile.d/...  Of course, that is an Arch thing, and we'll just have to work it out.

Except for any suggestions or guidance you might have about setting-up necessary environment variables for the build environment, this bug can be closed.