@ilya-fadin that is exactly what's happening. I got a HDR monitor a while back and tried it on plasma 6.4, and didn't realize that 6.10 completely changed stuff. Sure enough, removing the kde-unstable
repo and "rolling back" to stable, the package builds just fine. Thank you!
Search Criteria
Package Details: qt6ct-kde 0.10-2
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://www.opencode.net/trialuser/qt6ct |
Licenses: | BSD |
Conflicts: | qt6ct |
Provides: | qt6ct |
Submitter: | ilya-fedin |
Maintainer: | ilya-fedin |
Last Packager: | ilya-fedin |
Votes: | 30 |
Popularity: | 2.52 |
First Submitted: | 2023-11-08 18:16 (UTC) |
Last Updated: | 2025-07-29 21:03 (UTC) |
Dependencies (4)
Required by (5)
- catppuccin-qt5ct-git (requires qt6ct) (optional)
- dankmaterialshell-git (requires qt6ct) (optional)
- dms-shell (requires qt6ct) (optional)
- dms-shell-git (requires qt6ct) (optional)
- paperde (requires qt6ct)
Sources (2)
Zimmie commented on 2025-08-11 03:57 (UTC)
ilya-fedin commented on 2025-07-29 20:38 (UTC)
His Qt might be too new. 6.10 has changed the way private parts has to be requested but 6.10 isn't in stable repos nor qt6ct has adapted to it upstream.
FWIW, I think it's the time to rebase to the opencode upstream.
DrTebi commented on 2025-07-29 19:26 (UTC) (edited on 2025-07-29 19:32 (UTC) by DrTebi)
In response to @Zimmie: A long shot, but have you made sure that Qt6 has been updated before trying to install qt6ct? It sounds like it is referring to some libraries that don't exist (yet?).
Info on this page: https://doc.qt.io/qt-6/extras-changes-qt6.html#changes-to-qt-x11-extras ... may give some hints.
I have just downloaded this package and it built just fine, a couple of warnings, but no errors. My version of qt6 is 6.9.1-4. To check your version, run
pacman -Qi qt6-base
Zimmie commented on 2025-07-29 16:51 (UTC)
I can't get this to build, no matter what I try. Can anybody help? Here's the output:
CMake Error at src/qt6ct-qtplugin/CMakeLists.txt:12 (target_link_libraries):
Target "qt6ct-qtplugin" links to:
Qt6::GuiPrivate
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
CMake Error at src/qt6ct/CMakeLists.txt:34 (target_link_libraries):
Target "qt6ct" links to:
Qt6::GuiPrivate
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
v4u6h4n commented on 2025-04-07 06:38 (UTC)
@mortar1808
Thanks! That worked :-)
mortar1808 commented on 2025-04-05 07:12 (UTC)
Seems like the latest update to qt6 broke the theming for me. Rebuilding the package fixes it.
ilya-fedin commented on 2025-03-05 15:52 (UTC)
The new MR URL is https://www.opencode.net/trialuser/qt6ct/-/merge_requests/9
ilya-fedin commented on 2025-03-05 14:49 (UTC)
New qt6ct upstream is found https://www.opencode.net/trialuser/qt6ct
ilya-fedin commented on 2025-03-04 14:26 (UTC)
So it seems the repo got archived not at author's will but due to sanctions. Arch maintainers don't seem to want to switch upstream. If anyone has account on sourceforge, asking author what's the new upstream URL might be the only way forward.
More info at https://gitlab.archlinux.org/archlinux/packaging/packages/qt6ct/-/issues/1
KdU7aq commented on 2025-02-06 17:42 (UTC)
qt6ct got archived on github so I took the liberty to completely fork it. I released 0.10 on my repo, I wonder whether we can ask to switch official Arch package to it?
Indeed, it would be nice if this could replace current extra/qt6ct
which still uses archived upstream project.
Thank you for your work!
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