Package Details: qt5ct-kde 1.8-1

Git Clone URL: (read-only, click to copy)
Package Base: qt5ct-kde
Description: Qt5 Configuration Utility, patched to work correctly with KDE applications
Upstream URL:
Licenses: BSD
Conflicts: qt5ct
Provides: qt5ct
Submitter: ilya-fedin
Maintainer: ilya-fedin
Last Packager: ilya-fedin
Votes: 13
Popularity: 0.107585
First Submitted: 2021-07-11 08:02 (UTC)
Last Updated: 2023-11-08 18:09 (UTC)

Dependencies (3)

Required by (10)

Sources (2)

Pinned Comments

ilya-fedin commented on 2021-07-11 08:04 (UTC) (edited on 2021-07-11 08:19 (UTC) by ilya-fedin)

Some user guide:

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

  1. xdg-desktop-portal dialogs support
  2. KDE color schemes support
  3. KDE QML applications theming support
  4. 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 enviornment 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):

Latest Comments

1 2 3 Next › Last »

ilya-fedin commented on 2023-11-08 18:18 (UTC)

qt6ct-kde based on KF6 Arch packages is live

ilya-fedin commented on 2023-10-27 09:16 (UTC)

It has no Ethernet port

Kyuunex commented on 2023-10-26 21:12 (UTC)

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

ilya-fedin commented on 2023-10-22 02:26 (UTC) (edited on 2023-10-22 02:26 (UTC) by ilya-fedin)

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).

guiodic commented on 2023-10-20 09:38 (UTC)

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

juniorsupertux commented on 2023-05-13 05:24 (UTC)

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.

juniorsupertux commented on 2023-05-06 03:25 (UTC)

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.

ilya-fedin commented on 2023-05-01 11:29 (UTC)

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

juniorsupertux commented on 2023-05-01 11:27 (UTC)

I'm not sure if this backtrace helps: I also reported the bug to the audiotube dev to see if they can assist

ilya-fedin commented on 2023-05-01 10:33 (UTC)

qqc2-desktop-style uses Kirigami itself, so it can add additional Kirigami-related warnings likely. I can't help with crashes without backtraces though (obtaining which would likely involve rebuilding Qt, KDE libraries and applications themselves with debug symbols).