This package does not work for me (on neochat at least). I did a bit of debugging and found that using if(qApp->property("KDE_COLOR_SCHEME_PATH").toString().isEmpty())
instead of if(qApp->property("KDE_COLOR_SCHEME_PATH").isNull())
makes it work.
Search Criteria
Package Details: qt6ct-kde 0.10-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/qt6ct-kde.git (read-only, click to copy) |
---|---|
Package Base: | qt6ct-kde |
Description: | Qt 6 Configuration Utility, patched to work correctly with KDE applications |
Upstream URL: | https://github.com/ilya-fedin/qt6ct |
Licenses: | BSD |
Conflicts: | qt6ct |
Provides: | qt6ct |
Submitter: | ilya-fedin |
Maintainer: | ilya-fedin |
Last Packager: | ilya-fedin |
Votes: | 21 |
Popularity: | 2.02 |
First Submitted: | 2023-11-08 18:16 (UTC) |
Last Updated: | 2025-02-04 20:31 (UTC) |
Dependencies (3)
- qqc2-desktop-style (qqc2-desktop-style-gitAUR)
- cmake (cmake-gitAUR, cmake3AUR) (make)
- qt6-tools (make)
Required by (1)
- paperde (requires qt6ct)
Sources (1)
Latest Comments
« First ‹ Previous 1 2 3 4
q234rty commented on 2024-03-06 18:12 (UTC)
ilya-fedin commented on 2023-11-09 17:06 (UTC) (edited on 2023-11-09 17:07 (UTC) by ilya-fedin)
You're commenting under qt6ct-kde, not qt5ct-kde. The dependency is right
yochananmarqos commented on 2023-11-09 16:40 (UTC)
The dependency is now called qqc2-desktop-style5
with the recent renaming of the KF5 packages.
ilya-fedin commented on 2023-11-08 18:17 (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 qt6ct:
- KDE color schemes support
- KDE QML applications theming support
- 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 qt6ct, too).
To get them with plasma-integration:
- Install plasma-integration
- Choose KDE as standard dialogs in qt6ct configurator
To get them with xdg-desktop-portal-kde:
- Install xdg-desktop-portal + xdg-desktop-portal-kde
- Configure xdg-desktop-portal's FileChooser to
kde
, see https://wiki.archlinux.org/title/XDG_Desktop_Portal#Configuration - Ensure that session dbus instance is running correctly
- Choose XDG Desktop Portal as standard dialogs in qt6ct configurator
How to ensure that session dbus instance is running correctly when using xinit (DMs should already do the right thing for you):
- Ensure you don't have dbus-launch nor dbus-session-run in .xinitrc
- Ensure you copied the
for f in /etc/X11/xinit/xinitrc.d/?*.sh
loop from /etc/X11/xinit/xinitrc to your .xinitrc - 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
Pinned Comments
ilya-fedin commented on 2023-11-08 18:17 (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 qt6ct:
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 qt6ct, too).
To get them with plasma-integration:
To get them with xdg-desktop-portal-kde:
kde
, see https://wiki.archlinux.org/title/XDG_Desktop_Portal#ConfigurationHow to ensure that session dbus instance is running correctly when using xinit (DMs should already do the right thing for you):
for f in /etc/X11/xinit/xinitrc.d/?*.sh
loop from /etc/X11/xinit/xinitrc to your .xinitrcsystemctl --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