SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So how do you get the qt5ct utility to work? I issued the command:
Code:
set QT_QPA_PLATFORMTHEME=qt5ct
However in the qt5config window I just get "this application is not setup configured correctly." Did I have to set that command as root, or is it something completely different?
So how do you get the qt5ct utility to work? I issued the command:
Code:
set QT_QPA_PLATFORMTHEME=qt5ct
However in the qt5config window I just get "this application is not setup configured correctly." Did I have to set that command as root, or is it something completely different?
I add that line to /etc/environment, like this:
Code:
bash-5.1$ cat /etc/environment
# /etc/environment
# This file is parsed by pam_env module.
# This file may contain environment variable settings that should be used
# system-wide. Please note that it is not a script file and should only
# contain assignment expressions, one per line.
# The environment variables in this file will be loaded before those in other
# files such as: /etc/profile, /etc/profile.d/*, ~/.profile, etc.
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
QT_QPA_PLATFORMTHEME=qt5ct
# /etc/environment
# This file is parsed by pam_env module.
# This file may contain environment variable settings that should be used
# system-wide. Please note that it is not a script file and should only
# contain assignment expressions, one per line.
# The environment variables in this file will be loaded before those in other
# files such as: /etc/profile, /etc/profile.d/*, ~/.profile, etc.
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
QT_QPA_PLATFORMTHEME=qt5ct
I even restarted my KDE session, and qt5settings still says it is not configured properly.
One thing that is probably not related, but qt5ct-1.1 is a bit dated. The newest version is 1.5. Just grab the source and change the version line in the slackbuild. No other changes are needed. And make sure you put export in front of the line.
One thing that is probably not related, but qt5ct-1.1 is a bit dated. The newest version is 1.5. Just grab the source and change the version line in the slackbuild. No other changes are needed. And make sure you put export in front of the line.
Code:
export QT_QPA_PLATFORMTHEME=qt5ct
Ok I forgot export, but I grabbed 1.1 , compiled it , installed (upgraded), verified my /etc/environment
Code:
# /etc/environment
# This file is parsed by pam_env module.
# This file may contain environment variable settings that should be used
# system-wide. Please note that it is not a script file and should only
# contain assignment expressions, one per line.
# The environment variables in this file will be loaded before those in other
# files such as: /etc/profile, /etc/profile.d/*, ~/.profile, etc.
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
export QT_QPA_PLATFORMTHEME=qt5ct
And I even have the same in /etc/profile.d/qt5.sh
Code:
#!/bin/sh
# Environment variables for the Qt package.
#
# It's best to use the generic directory to avoid
# compiling in a version-containing path:
if [ -d /usr/lib64/qt5 ]; then
QT5DIR=/usr/lib64/qt5
else
# Find the newest Qt directory and set $QT5DIR to that:
for qtd in /usr/lib64/qt5-* ; do
if [ -d $qtd ]; then
QT5DIR=$qtd
fi
done
fi
PATH="$PATH:$QT5DIR/bin"
export QT5DIR
export QT_QPA_PLATFORMTHEME=qt5ct
# Unfortunately Chromium and derived projects (including QtWebEngine) seem
# to be suffering some bitrot when it comes to 32-bit support, so we are
# forced to disable the seccomp filter sandbox on 32-bit or else all of these
# applications crash. If anyone has a patch that gets these things running on
# 32-bit without this workaround, please let volkerdi or alienBOB know, or
# post your solution on LQ. Thanks. :-)
if file /bin/cat | grep -wq 32-bit ; then
export QTWEBENGINE_CHROMIUM_FLAGS="--disable-seccomp-filter-sandbox"
fi
I've got the same thing as Daedra in my ~/.xsession which is used by XDM/xinit to start X.
Works fine, qt5-5.15.3_20220312_33a3f16f-x86_64 & qt5ct-1.5-x86_64
Note you must recompile qt5ct every time when qt is upgraded.
Also note, some programs like virtualbox ship static qt which you cannot theme with qt5ct.
Make sure there isn't something else that sets QT_QPA_PLATFORMTHEME on your system.
Maybe there's some export like that in 'startkde' now, but I don't use kde so..
Does it work in xfce, or with a simple wm? Without starting a plasma session I mean.
I've got the same thing as Daedra in my ~/.xsession which is used by XDM/xinit to start X.
Works fine, qt5-5.15.3_20220312_33a3f16f-x86_64 & qt5ct-1.5-x86_64
Note you must recompile qt5ct every time when qt is upgraded.
Also note, some programs like virtualbox ship static qt which you cannot theme with qt5ct.
Make sure there isn't something else that sets QT_QPA_PLATFORMTHEME on your system.
Maybe there's some export like that in 'startkde' now, but I don't use kde so..
Does it work in xfce, or with a simple wm? Without starting a plasma session I mean.
I haven't tried it in xfce, but so now from what I am understanding I need to go and remove the export command in /etc/environment and /etc/profile.d/qt5.sh ...and just put it in my .xsession... Ok I will try that. I also never upgraded qt5 so recompiling anything is moot.
Mine (v1.5) just works, style:fusion dialogs:default palette:custom font:roboto
If compiled against the specific qt5 version you have installed then it should just work. Note that v1.1 may be older than qt5 in slackware 15.
And BTW .xsession is only executed in some setups not all, almost certain here that kde disregards that.
Anyway, easy enough to check with "env" where it lists all variables, if QT_QPA_PLATFORMTHEME is listed.
What does it say if you run "qt5ct" from the terminal?
Mine (v1.5) just works, style:fusion dialogs:default palette:custom font:roboto
If compiled against the specific qt5 version you have installed then it should just work. Note that v1.1 may be older than qt5 in slackware 15.
And BTW .xsession is only executed in some setups not all, almost certain here that kde disregards that.
Anyway, easy enough to check with "env" where it lists all variables, if QT_QPA_PLATFORMTHEME is listed.
What does it say if you run "qt5ct" from the terminal?
I am just running the stock qt5 included in Slackware 15. I honestly do not know, since clearly it isn't 'just working' for me and I am at the verge of saying fsck this and giving up but here is the terminal output anyhow:
If you want my advice, compile qt5ct-1.5 which Daedra already confirmed working,
Other than that, I don't know, only time I've had a problem with it was when virtualbox set QT_QPA_PLATFORMTHEME=xcb by force.
So yeah, if you run virtualbox it's not going to work, you'll have to logout and reset the variable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.