Arch Linux User Repository

Some user guide:

My patchset contains multiple fixes/features in comparison to vanilla qt5ct:

1. KDE color schemes support
2. KDE QML applications theming support
3. KDE's icon engine is used, fixing monochrome icons colors (I saw problems with e.g. Adapta Kvantum theme on KDE applications toolbars, like dolphin, they're grey when should be white)

xdg-desktop-portal allows you to have KDE dialogs in non-KDE environment without installing plasma-integration package. To get them, all you need is:

1. Install xdg-desktop-portal + xdg-desktop-portal-kde
2. If you have xdg-desktop-portal-gtk installed, rename usr/share/xdg-desktop-portal/portals/gtk.portal to zz-gtk.portal (backend priority is in alphabetical order). You can add that file to NoExtract in pacman.conf.
3. Ensure that session dbus instance is running correctly.

How to ensure that session dbus instance is running correctly when using xinit (DMs should already do the right thing for you):

1. Ensure you don't have dbus-launch nor dbus-session-run in .xinitrc
2. Ensure you copied the for f in /etc/X11/xinit/xinitrc.d/?*.sh loop from /etc/X11/xinit/xinitrc to your .xinitrc
3. Ensure you have no errors in systemctl --user status dbus and the service is running. You shouldn't enable the service, it should be activated by dbus.socket.

In case of Wayland, you may need to integrate your WM with systemd (that's what one of the scripts in /etc/X11/xinit/xinitrc.d does for X11): https://github.com/swaywm/sway/wiki#gtk-applications-take-20-seconds-to-start

Are you sure you have binutils installed?

I tried to install it, but I failed at makepkg part. It is said that can't find ld, but the ld just works fine on my computer. The full log:

==> Making package: qt5ct-kde 1.8-4 (Tue 28 May 2024 07:00:56 PM CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found qt5ct-1.8.tar.bz2
  -> Found qt5ct-shenanigans.patch
==> Validating source files with sha256sums...
    qt5ct-1.8.tar.bz2 ... Passed
    qt5ct-shenanigans.patch ... Passed
==> Extracting sources...
  -> Extracting qt5ct-1.8.tar.bz2 with bsdtar
==> Starting prepare()...
patching file CMakeLists.txt
patching file src/qt5ct/CMakeLists.txt
patching file src/qt5ct/appearancepage.cpp
patching file src/qt5ct-common/qt5ct.cpp
patching file src/qt5ct-qtplugin/CMakeLists.txt
patching file src/qt5ct-qtplugin/qt5ctplatformtheme.cpp
patching file src/qt5ct-qtplugin/qt5ctplatformtheme.h
==> Starting build()...
-- The CXX compiler identification is GNU 14.1.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ - broken
CMake Error at /usr/share/cmake/Modules/CMakeTestCXXCompiler.cmake:73 (message):
  The C++ compiler

    "/usr/bin/c++"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: '/tmp/makepkg/qt5ct-kde/src/build/CMakeFiles/CMakeScratch/TryCompile-Tzn5pO'

    Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1 /usr/bin/make -f Makefile cmTC_31495/fast
    /usr/bin/make  -f CMakeFiles/cmTC_31495.dir/build.make CMakeFiles/cmTC_31495.dir/build
    make[1]: Entering directory '/tmp/makepkg/qt5ct-kde/src/build/CMakeFiles/CMakeScratch/TryCompile-Tzn5pO'
    Building CXX object CMakeFiles/cmTC_31495.dir/testCXXCompiler.cxx.o
    /usr/bin/c++   -march=native -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -g -ffile-prefix-map=/tmp/makepkg/qt5ct-kde/src=/usr/src/debug/qt5ct-kde -flto=auto  -o CMakeFiles/cmTC_31495.dir/testCXXCompiler.cxx.o -c /tmp/makepkg/qt5ct-kde/src/build/CMakeFiles/CMakeScratch/TryCompile-Tzn5pO/testCXXCompiler.cxx
    Linking CXX executable cmTC_31495
    /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_31495.dir/link.txt --verbose=1
    /usr/bin/c++ -march=native -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -g -ffile-prefix-map=/tmp/makepkg/qt5ct-kde/src=/usr/src/debug/qt5ct-kde -flto=auto  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fuse-ld=mold -flto=auto  CMakeFiles/cmTC_31495.dir/testCXXCompiler.cxx.o -o cmTC_31495
    collect2: fatal error: cannot find ‘ld’
    compilation terminated.
    make[1]: *** [CMakeFiles/cmTC_31495.dir/build.make:99: cmTC_31495] Error 1
    make[1]: Leaving directory '/tmp/makepkg/qt5ct-kde/src/build/CMakeFiles/CMakeScratch/TryCompile-Tzn5pO'
    make: *** [Makefile:127: cmTC_31495/fast] Error 2





  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)


-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...

qt6ct-kde based on KF6 Arch packages is live

It has no Ethernet port

@ilya-fedin you could try using Wake-on-LAN to power your laptop without a power button. This feature is sometimes on by default.

I have a configured AUR development environment only on my laptop that is not working due to a broken power on button which is a part of the integrated keyboard. It's likely that I won't set up AUR environment on my desktop and will wait until I get a new keyboard (should be 5th November).

qqc2-desktop-style is no more in repos, please replace it with qqc2-desktop-style5

I found the source of the problem. Unsetting the QT_QUICK_CONTROLS_STYLE variable or setting it to org.kde.desktop fixes all the issues. I had it set to Plasma to maintain coherence with QtQuick 1 since some KDE apps uses it and there isn't a qqc-desktop-style. By looking at the patch, this patched version of qt5ct seems to use org.kde.desktop, so I guess they interfere. Sorry for all the hassle caused so far.

Forgot to mention that this does not seem to happen with vanilla Kvantum, though those KDE QtQuick apps which works looks better with this patch.

No, sadly it's made without debug symbols, but it seem to look like a Qt bug.