Package Details: qt5ct-kde 1.8-15

Git Clone URL: https://aur.archlinux.org/qt5ct-kde.git (read-only, click to copy)
Package Base: qt5ct-kde
Description: Qt5 Configuration Utility, patched to work correctly with KDE applications
Upstream URL: https://qt5ct.sourceforge.io/
Licenses: BSD
Conflicts: qt5ct
Provides: qt5ct
Submitter: ilya-fedin
Maintainer: ilya-fedin
Last Packager: ilya-fedin
Votes: 19
Popularity: 0.44
First Submitted: 2021-07-11 08:02 (UTC)
Last Updated: 2024-10-25 18:56 (UTC)

Dependencies (3)

Required by (10)

Sources (2)

Pinned Comments

ilya-fedin commented on 2025-02-17 06:27 (UTC) (edited on 2025-02-17 06:28 (UTC) by ilya-fedin)

Looks like it's over, Plasma 5 is removed from the repos. Now the only things possible to do are to remove the package somehow (how? I don't see such a button) or to wait, maybe someone will re-package the deps in the AUR.

ilya-fedin commented on 2021-07-11 08:04 (UTC) (edited on 2025-03-04 14:40 (UTC) by ilya-fedin)

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)

It's important to set a KDE color scheme (marked as (KColorScheme) in the list) for proper theming of KDE apps.

Additionally, if one wants KDE dialogs, this could be reached either with plasma-integration or xdg-desktop-portal (both work with vanilla qt5ct, too).

To get them with plasma-integration:

  1. Install plasma-integration
  2. Choose KDE as standard dialogs in qt5ct configurator

To get them with xdg-desktop-portal-kde:

  1. Install xdg-desktop-portal + xdg-desktop-portal-kde
  2. Configure xdg-desktop-portal's FileChooser to kde, see https://wiki.archlinux.org/title/XDG_Desktop_Portal#Configuration
  3. Ensure that session dbus instance is running correctly
  4. Choose XDG Desktop Portal as standard dialogs in qt5ct configurator

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

Latest Comments

« First ‹ Previous 1 2 3 4

ilya-fedin commented on 2022-09-12 16:19 (UTC)

Would be nice to get stack trace

DroidFreak32 commented on 2022-09-11 10:52 (UTC)

While this works great on non KDE environments, it seems to break KDE itself in some cases.

Ex running systemsettings5:

Using fontconfig file: "/home/horcrux/.config/fontconfig/fonts.conf"
kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/mailto" not found
kf.coreaddons: "Could not load plugin from kcm_kaccounts: The shared library was not found."
kf.coreaddons: "Could not load plugin from kcm_kscreen: The shared library was not found."
kf.coreaddons: "Could not load plugin from kcm_pulseaudio: The shared library was not found."
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
[1]    41752 segmentation fault (core dumped)  systemsettings5

UN-setting QT_QPA_PLATFORMTHEME works, however, this isn't needed in the vanilla qt5ct package (which instead messes up the font and colors)

Kaos_Bunny commented on 2022-02-07 23:22 (UTC) (edited on 2022-02-07 23:33 (UTC) by Kaos_Bunny)

For adding the file to NoExtract in pacman.conf (as mentioned in the pinned comment), is this a hard requirement (what will happen if it's not done), and am I doing this correctly?

NoExtract = usr/share/xdg-desktop-portal/portals/zz-gtk.portal

Also, for the session dbus check, I'm getting this error but it's still active (triggered by dbus.socket). Is this okay?

digital_mystik commented on 2021-09-05 18:21 (UTC)

this package is awesome! I have been exporting KDE as my DE in sway but it was messing with a few things, and vanilla qt5ct couldn't match my regular setup; really glad I stumbled upon this

yochananmarqos commented on 2021-07-11 16:51 (UTC)

This should provide and conflict with qt5ct.

ilya-fedin commented on 2021-07-11 08:04 (UTC) (edited on 2025-03-04 14:40 (UTC) by ilya-fedin)

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)

It's important to set a KDE color scheme (marked as (KColorScheme) in the list) for proper theming of KDE apps.

Additionally, if one wants KDE dialogs, this could be reached either with plasma-integration or xdg-desktop-portal (both work with vanilla qt5ct, too).

To get them with plasma-integration:

  1. Install plasma-integration
  2. Choose KDE as standard dialogs in qt5ct configurator

To get them with xdg-desktop-portal-kde:

  1. Install xdg-desktop-portal + xdg-desktop-portal-kde
  2. Configure xdg-desktop-portal's FileChooser to kde, see https://wiki.archlinux.org/title/XDG_Desktop_Portal#Configuration
  3. Ensure that session dbus instance is running correctly
  4. Choose XDG Desktop Portal as standard dialogs in qt5ct configurator

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