Difference between revisions of "Uniform look for Qt and GTK applications"

From ArchWiki
Jump to: navigation, search
(rewrote the section on QGtkStyle and included a brief help section for non-GNOME people)
(After system upgrade breeze icons are missing in GTK apps. Found solution here: https://bbs.archlinux.org/viewtopic.php?id=107465 This is second time I faced to this issue)
(233 intermediate revisions by 90 users not shown)
Line 1: Line 1:
[[Category:Desktop environments (English)]]
+
[[Category:Widget toolkits]]
[[Category:HOWTOs (English)]]
+
[[Category:Eye candy]]
[[Category:Eye candy (English)]]
+
[[es:Uniform look for Qt and GTK applications]]
{{i18n_links_start}}
+
[[it:Uniform look for Qt and GTK applications]]
{{i18n_entry|English|Uniform look for QT and GTK apps}}
+
[[ja:Qt と GTK アプリケーションの外観の統合]]
{{i18n_entry|简体中文|QT和GTK程序统一外观}}
+
[[ru:Uniform look for Qt and GTK applications]]
{{i18n_links_end}}
+
[[zh-hans:Uniform look for Qt and GTK applications]]
= Introduction =
+
{{Related articles start}}
 +
{{Related|GTK+}}
 +
{{Related|Qt}}
 +
{{Related articles end}}
 +
[[Qt]] and [[GTK+]] based programs both use a different widget toolkit to render the graphical user interface. Each come with different themes, styles and icon sets by default, among other things, so the "look and feel" differ significantly. This article will help you make your Qt and GTK+ applications look similar for a more streamlined and integrated desktop experience.
  
[http://en.wikipedia.org/wiki/Qt_(toolkit) Qt]- and [[GTK+]] -based programs both use a different widget toolkit to render the graphical user interface. Each come with different themes, styles and icon sets by default, among other things, so the "look and feel" differ significantly. This article will help you make your Qt and GTK+ applications look similar for a more streamlined and "integrated" desktop experience.
+
== Overview ==
  
''"Qt (pronounced "cute") is a cross-platform application development framework, widely used for the development of GUI programs (in which case it is known as a Widget toolkit), and also used for developing non-GUI programs such as console tools and servers."''
+
To get a similar look between the toolkits, you will most likely have to modify the following:
 +
* '''Theme''': The custom appearance of an application, widget set, etc. It usually consists of a style, an icon theme and a color theme.
 +
* '''Style''': The graphical layout and look of the widget set.
 +
* '''Icon Theme''': A set of global icons.
 +
* '''Color Theme''': A set of global colors that are used in conjunction with the style.
  
*'''Theme''' - Collection of a style, an icon theme and a colour theme.
+
You can choose various approaches:
*'''Style''' - Graphical layout; look.
+
* Modify [[#Styles for both Qt and GTK+|GTK+ and Qt styles]] separately with the tools listed below for each toolkit and aim for choosing similarly looking themes (style, colors, icons, cursors, fonts).
*'''Icon Theme''' - Set of global icons.
+
* Use a special [[#Theme engines|theme engine]], which intermediates the modification of the other graphical toolkit to match your main toolkit.
*'''Colour Theme''' - Set of global colours that are used in conjunction with the style.
 
  
= Styles =
+
== Styles for both Qt and GTK+ ==
 +
There are widget style sets available for the purpose of integration, where builds are written and provided for both Qt and GTK+, all major versions included. With these, you can have one look for all applications regardless of the toolkit they had been written with.
  
There are widget style sets available for the purpose of integration, where builds are written and provided for both Qt and GTK+, all major versions included. With these, you can have one look for all applications regardless of the toolkit they had been written with.
+
{{Tip|You may want to apply user defined styles to root applications, see [[GTK#Theme not applied to root applications]] and [[Qt#Theme not applied to root applications]].}}
 +
{{Note|1=Since version 3.16, GTK+ 3 [https://bbs.archlinux.org/viewtopic.php?pid=1518404#p1518404 does not support] non-CSS themes, hence previous solutions such as Oxygen-Gtk are [https://bugs.kde.org/show_bug.cgi?id=340288 no longer viable] options.}}
 +
 
 +
=== Breeze ===
 +
 
 +
Breeze is the default Qt style of KDE Plasma. It can be installed with the {{Pkg|breeze}} package for Qt5, the {{Pkg|breeze-kde4}} package for Qt4, and the {{Pkg|breeze-gtk}} package for GTK+ 2 and GTK+ 3.
 +
 
 +
Once installed, you can use one of the many [[GTK+#Configuration tools|GTK+ configuration tools]] to change the GTK+ theme.
 +
 
 +
=== Adwaita ===
 +
 
 +
Adwaita is the default GNOME theme. The GTK+ 3 version is included in the {{Pkg|gtk3}} package, while the GTK+ 2 version is in {{Pkg|gnome-themes-standard}}. [https://github.com/MartinBriza/adwaita-qt adwaita-qt] is a Qt port of the Adwaita theme. Unlike [[#QGtkStyle]], which mimics the GTK+ 2 theme, it provides a native Qt style made to look like the GTK+ 3 Adwaita. It can be [[install|installed]] with the {{AUR|adwaita-qt4}} and {{AUR|adwaita-qt5}} packages for the Qt 4 and 5 versions, respectively.
 +
 
 +
To set the Qt style as default:
 +
 
 +
* For Qt4, it can be enabled with ''Qt Configuration'' ({{ic|qtconfig-qt4}}), choose ''adwaita'' under ''Appearance > GUI Style''. Alternatively, edit the {{ic|/etc/xdg/Trolltech.conf}} (system-wide) or {{ic|~/.config/Trolltech.conf}} (user-specific) file:
 +
 
 +
{{hc|~/.config/Trolltech.conf|2=
 +
...
 +
[Qt]
 +
style=adwaita
 +
...
 +
}}
 +
 
 +
* For Qt 5, it can be enabled by setting the following [[Environment variables#Graphical applications|environment variable]]: {{ic|1=QT_STYLE_OVERRIDE=adwaita}}. Alternatively, use {{Pkg|qt5ct}} package. For more detailed instructions, see [[Qt#Configuration of Qt5 apps under environments other than KDE Plasma]].
 +
 
 +
== Theme engines ==
 +
 
 +
A ''theme engine'' can be thought of as a thin layer API which translates themes (excluding icons) between one or more toolkits. These engines add some extra code in the process and it is arguable that this kind of a solution is not as elegant and optimal as using native styles.
 +
 
 +
=== QGtkStyle ===
  
== Changing Styles ==
+
{{Note|QGtkStyle has been removed from {{Pkg|qt5-base}} 5.7.0 [https://github.com/qtproject/qtbase/commit/899a815414e95da8d9429a4a4f4d7094e49cfc55] and added to {{Pkg|qt5-styleplugins}} [https://github.com/qtproject/qtstyleplugins/commit/102da7d50231fc5723dba6e72340bef3d29471aa]}}
  
To change the style of Qt3 and KDE3 applications in KDE3:
+
{{Warning|Depending on GTK+ 2 theme, this style may cause rendering issues such as transparent fonts or inconsistent widgets.}}
:''Control Center (kcontrol) --> Appearance & Themes --> Style''
 
  
To change the style of Qt3 applications outside of KDE3
+
This Qt style uses GTK+ 2 to render all components to blend in with [[GNOME]] and similar GTK+ based environments. Beginning with Qt 4.5, this style is included in Qt. It requires {{Pkg|gtk2}} to be installed and configured.
:''Qt Configuration (qt3config) --> Appearance --> Select GUI Style''
 
  
To change the style of Qt4 and KDE4 applications in KDE4:
+
This is the default Qt4 style in Cinnamon, GNOME and Xfce, and the default Qt5 style in Cinnamon, GNOME, MATE, LXDE and Xfce. In other environments:
:''System Settings (systemsettings) --> Appearance --> Style''
 
  
To change the style of Qt4 applications outside of KDE4
+
* For Qt4, it can be enabled with ''Qt Configuration'' ({{ic|qtconfig-qt4}}), choose ''GTK+'' under ''Appearance > GUI Style''. Alternatively, edit the {{ic|/etc/xdg/Trolltech.conf}} (system-wide) or {{ic|~/.config/Trolltech.conf}} (user-specific) file:
:''Qt Configuration (qtconfig) --> Appearance --> Select GUI Style''
 
  
To change the GTK+ version 2 style in KDE3:
+
{{hc|~/.config/Trolltech.conf|2=
# pacman -Sy gtk-chtheme
+
...
 +
[Qt]
 +
style=GTK+
 +
...
 +
}}
  
Run it and you will be able to make your choice. You can also change the fonts. Please note that any open application must be restarted in order to view the changes. Alternatively, you can do the same with an engine, mentioned further below.
+
* For Qt 5, it can be enabled by installing {{Pkg|qt5-styleplugins}} and setting the following [[Environment variables#Graphical applications|environment variable]]: {{ic|1=QT_QPA_PLATFORMTHEME=gtk2}}
  
 +
For full uniformity, make sure that the configured [[GTK+#Themes|GTK+ theme]] supports both GTK+ 2 and GTK+ 3. If your preferred theme has inconsistent rendering after configuring Qt to use GTK+2, install {{ic|gtk-theme-switch2}} and choose a theme.
  
== QtCurve ==
+
=== QGnomePlatform ===
  
Available for ''qt4'' (kde4), ''qt3'' (kde3), and ''gtk2'' (gnome) in the '''[extra]''' repository, this highly-configurable style is the most popular all-rounder. It has many controls for various options, ranging from the appearance of buttons to the shape of sliders. You can install all of them using pacman.
+
This Qt 5 platform theme applies the appearance settings of GNOME for Qt applications. It can be installed with the {{AUR|qgnomeplatform}} package or the {{AUR|qgnomeplatform-git}} package for the development version. It does not provide a Qt style itself, instead it requires a [[#Styles for both Qt and GTK+|style that support both Qt and GTK+]].
# pacman -Sy qtcurve-gtk2 qtcurve-kde3 qtcurve-kde4
 
  
== KDE4 Oxygen ==
+
This platform theme is enabled automatically in GNOME since version 3.20. For other systems, it can be enabled by setting the following [[Environment variables#Graphical applications|environment variable]]: {{ic|1=QT_QPA_PLATFORMTHEME=qgnomeplatform}}.
  
QT4 version installs with kde.
+
== Tips and tricks ==
GTK version available via AUR http://aur.archlinux.org/packages.php?ID=24329 or http://aur.archlinux.org/packages.php?ID=18967
+
=== KDE file dialogs for GTK+ applications ===
 +
'''Chromium''' 
 +
At least for chromium installing {{ic|kdialog}} makes chromium used kde file dialog ( so `KGtk-wrapper` is not required )
  
== Others ==
+
{{Warning|Some GTK+ applications may not be compatible with KGtk-wrapper (e.g. [[Chromium]]), sometimes the wrapper makes the application crash ([[Firefox]] or [[Thunderbird]]).}}
  
Similar style sets are those that look like each other - written and provided for both Qt and GTK+ - but are not necessarily from the same developers. You may have to do some minor tweaking to make them look the same. Below is a list:
+
{{AUR|kgtk}} from the [[AUR]] is a wrapper script which uses {{ic|LD_PRELOAD}} to force KDE file dialogs in GTK+ 2.x apps. Once installed you can run GTK+ 2.x applications with {{ic|kgtk-wrapper}} in two ways (using [[GIMP]] in the examples):
  
*klearlooks (qt3); clearlooks (gtk2)
+
* Calling {{ic|kgtk-wrapper}} directly and using the GTK+ 2.x binary as an argument:
 +
:{{bc|$ /usr/bin/kgtk-wrapper gimp}}
 +
* Modifying the KDE .desktop shortcuts files you can find at {{ic|/usr/share/applications/}} to prefix the {{ic|Exec}} statement with kgtk-wrapper.
 +
:e.g. with [[GIMP]], edit the {{ic|/usr/share/applications/gimp.desktop}} shortcut file and replace {{ic|1=Exec=gimp-2.8 %U}} by {{ic|1=Exec=kgtk-wrapper gimp-2.8 %U}}.
  
= Theme Engines =
+
=== Using a GTK+ icon theme in Qt apps ===
  
A Theme Engine can be thought of as a thin layer API which translates themes (excluding icons) between one or more toolkits. These engines add some extra code in the process and it is arguable that this kind of a solution is not as elegant and optimal as using native styles.
+
{{Style|Duplicates [[environment variables]]}}
  
== GTK-QT-Engine ==
+
If you are running Plasma, install {{Pkg|kde-gtk-config}} and select the icon-theme under ''System Settings > Application Style > GTK''.
  
This one is for use by GTK+ applications running in KDE, which basically means this is for KDE. It applies all Qt settings (styles, fonts, not icons though) to the GTK+ applications and uses the style plug-ins directly. Please note that there are rendering issues with some Qt styles.
+
If you are using [[GNOME]], first check if {{Pkg|dconf-editor}} is installed.
  
# pacman -Sy gtk-qt-engine
+
Then, run {{ic|dconf-editor}} and look under ''org > gnome > desktop > interface'' for {{ic|icon-theme}} key and change it to your preferred icon theme.
  
You can access it from:
+
If you are not using [[GNOME]], for example if you are running a minimal system with {{Pkg|i3-wm}}, first install {{Pkg|dconf-editor}}.
:''Control Center (kcontrol) --> Appearance & Themes --> GTK Styles and Fonts''
 
  
If you want to remove it entirely and every trace of it, you should delete the following files:
+
Then, run {{ic|dconf-editor}} and look under ''org > gnome > desktop > interface'' for {{ic|icon-theme}} key and change it to your preferred icon theme.
  
*~/.gtkrc2.0-kde
+
Since, you are not using [[GNOME]], you might have to set the value of {{ic|DESKTOP_SESSION}} in your profile. To do that execute the below code in a terminal and restart your system.
*~/.kde/env/gtk-qt-engine.rc.sh
 
*~/gtk-qt-engine.rc
 
  
=== Make it work with OpenOffice ===
+
  $ echo 'export DESKTOP_SESSION=gnome' >> /etc/profile
Set (as root):
 
  export SAL_GTK_USE_PIXMAPPAINT=1
 
into /etc/profile. In KDE4 systemsettings, make sure "use my KDE style in GTK applications" is selected in Appearance > GTK styles and fonts.
 
  
== QGtkStyle ==
+
'''OR'''
  
This is a Qt style which intends to make applications blend perfectly into the GNOME desktop environment by using GTK to render all components. To use this style you must have at least GTK+ 2.0 and Qt 4.3, although Qt 4.4 or higher is preferred.
+
Set {{ic|1=export DESKTOP_SESSION=gnome}} somewhere in your {{ic|~/.xinitrc}} or, if you are using a [[Display manager]] in [[Xprofile]].
  
{{Note|Beginning with version 4.5 this style is included in Qt. You don't have to install this package yourself, but there is an entry in the AUR for those still interested: [[http://aur.archlinux.org/packages.php?ID=16964 qgtkstyle-svn]].}}
+
{{Note| If the icon theme was not applied, you might want to check if the name that you entered of your preferred theme, was in the correct format. For example, if you want to apply the currently active icon theme to your QT applications, you can find the correct format of it's name with the command:
  
===Having trouble making your Qt applications use QGtkStyle?===
+
{{bc|1=$ cat ~/.gtkrc-2.0 {{!}} grep icon-theme {{!}} cut -d= -f2}}
  
Qt won't apply QGtkStyle correctly if GTK is using the [[Uniform_look_for_QT_and_GTK_apps#GTK-QT-Engine|GTK-QT-Engine]]. Qt determines whether the [[Uniform_look_for_QT_and_GTK_apps#GTK-QT-Engine|GTK-QT-Engine]] is in use by reading the GTK configuration files listed in the environmental variable '''GTK2_RC_FILES'''. If the environmental variable is not set properly, Qt assumes you are using the [[Uniform_look_for_QT_and_GTK_apps#GTK-QT-Engine|GTK-QT-Engine]], sets QGtkStyle to use the style GTK style ''Clearlooks'', and outputs an error message:
+
}}
  
QGtkStyle cannot be used together with the GTK_Qt engine.
+
=== Improve subpixel rendering of GTK apps under KDE Plasma ===
  
Users of [[Openbox]] and other non-GNOME environments may encounter this probem. Here is a solution:
+
See [[Font configuration#LCD filter]].
  
*Tell Qt where to look for your GTK configuration file by adding the following to your {{Filename|.xinitrc}} file:
+
== Troubleshooting ==
**To add multiple paths, separate them with colons.
 
**The `pwd` part will expand to be path to your user's home directory. Using the ~ shortcut won't work.
 
{{File|name=.xinitrc|content=...
 
export GTK2_RC_FILES="`pwd`/.gtkrc-2.0"
 
...}}
 
  
*In {{Filename|.gtkrc-2.0}} you must specify a GTK theme. For example:
+
=== Qt applications do not use QGtkStyle ===
**This is usually done for you by an [[Uniform_look_for_QT_and_GTK_apps#GTK2_styles|application which sets GTK2 Styles]]
+
Qt will not apply QGtkStyle correctly if GTK+ is using the [[#GTK+-Qt Engine|GTK+-Qt Engine]]{{Broken section link}}. Qt determines whether the GTK+-Qt Engine is in use by reading the GTK+ configuration files listed in the environmental variable {{ic|GTK2_RC_FILES}}. If the environmental variable is not set properly, Qt assumes you are using the engine, sets QGtkStyle to use the style GTK+ style ''Clearlooks'', and outputs an error message:
{{File|name=.gtkrc-2.0|content=...
 
gtk-theme-name="Crux"
 
...}}
 
  
== MetaTheme ==
+
QGtkStyle cannot be used together with the GTK_Qt engine.
  
The metatheme engine is designed as a thin layer between toolkits, creating a unified API by which each theme engine can draw. The result is that every application uses the same code for drawing, making the appearance same across different applications. This engine supports the GTK2, QT/KDE, and Java toolkits.
+
Another error you may get after launching {{ic|qtconfig-qt4}} from a shell and selecting the GTK+ style is:
# pacman -Sy metatheme
 
  
To install..
+
QGtkStyle was unable to detect the current GTK+ theme.
$ metatheme-install
 
  
To configure settings..
+
According to [https://bbs.archlinux.org/viewtopic.php?id=99175&p=1 this thread], you may simply have to install {{AUR|libgnomeui}} to solve this issue. This has the added benefit that you do not need to edit a file every time you change your theme via a graphical tool, like the one provided by xfce.
$ mt-config
 
  
To uninstall..
+
Users of [[Openbox]] and other non-GNOME environments may encounter this problem. To solve this, first add the following to your {{ic|.xinitrc}} file:
$ metatheme-install -u
+
{{hc|.xinitrc|<nowiki>
 +
...
 +
export GTK2_RC_FILES="$HOME/.gtkrc-2.0"
 +
...
 +
</nowiki>}}
  
= Other Tricks =
+
{{Note|
== KDE file dialogs for GTK2 apps ==
+
* Make sure to add this line before invoking the window manager.
KGtk is a wrapper script that LD_PRELOAD to force KDE file dialogs (open, save, etc) in GTK2 apps. If you use KDE and prefer its file dialogs over GTK's then you can install kgtk from AUR.  Once installed you can run GTK2 applications with kgtk-wrapper in 2 ways (using gimp in the examples).
+
* You can add multiple paths by separating them with colons.
 +
* Make sure to use {{ic|$HOME}} instead of {{ic|~}} as it will not properly expand to the user's home directory.
 +
}}
  
Calling kgtk-wrapper directly and using the GTK2 binary as an arguement
+
Then specify the theme you want in the {{ic|~/.gtkrc-2.0}} file using a [[#GTK2 styles|dedicated application]]{{Broken section link}} or manually, by adding:
/usr/local/bin/kgtk-wrapper gimp
+
{{hc|.gtkrc-2.0|<nowiki>
 +
...
 +
gtk-theme-name="[name of theme]"
 +
...
 +
</nowiki>}}
  
OR
+
Some tools only insert the following include directive in {{ic|~/.gtkrc-2.0}}:
 +
{{hc|.gtkrc-2.0|
 +
...
 +
include "/usr/share/themes/SomeTheme/gtk-2.0/gtkrc"
 +
...
 +
}}
 +
 +
which apparently is not recognized by all versions of QGtkStyle. You can hotfix this problem by inserting the {{ic|gtk-theme-name}} manually in your {{ic|~/.gtkrc-2.0}} file like above.
  
Creating a symbolic link to kgtk using the name of the GTK2 binary.  Then you can run /usr/local/bin/gimp when you want to run gimp with KDE dialogs.
+
{{Note|Style-changing applications will most probably rewrite the {{ic|~/.gtkrc-2.0}} file the next time you change themes.}}
ln -s /usr/local/bin/kgtk-wrapper /usr/local/bin/gimp
 
/usr/local/bin/gimp
 
  
== aMSN GTK or KDE dialogs ==
+
If these steps do not work, install {{Pkg|gconf}} and run this command:
aMSN's TK file dialogs are plain looking but no fear there is a plugin that will allow you to use GTK or KDE file dialogs to match your desktop.  You can find the plugin on [http://www.amsn-project.net/plugins.php aMSN's Plugin Page]
 
  
= Troubleshooting =
+
gconftool-2 --set --type string /desktop/gnome/interface/gtk_theme [name of theme]
  
== How do I set styles for each toolkit? ==
+
If you further want to set the same icon and cursor theme, then you have to specify them, too.
  
You can use the following methods to change the theme used in each environment.
+
gconftool-2 --set --type string /desktop/gnome/interface/icon_theme Faenza-Dark
  
==== KDE3 and QT3 styles ====
+
This sets the icon theme to Faenza-Dark located in {{ic|/usr/share/icons/Faenza-Dark}}. For the cursor theme you first have to set the gconf value.
* Control Center (kcontrol) --> Appearance & Themes --> Style --> Widget Style
 
* kde-config --style [name of style]
 
* /opt/qt/bin/qtconfig
 
  
==== QT4 styles ====
+
gconftool-2 --set --type string /desktop/gnome/peripherals/mouse/cursor_theme Adwaita
* /usr/bin/qtconfig
 
  
==== GTK2 styles ====
+
Then you will have to create the file {{ic|/usr/share/icons/default/index.theme}} with the following lines:
* gtk-chtheme
 
* gtk2_prefs
 
* switch2 (gtk-theme-switch2 package)
 
* lxappearance
 
  
==== GTK1 styles ====
+
[Icon Theme]
* switch (gtk-theme-switch package)
+
Inherits=Adwaita
  
== Themes not working in GTK apps ==
+
=== Themes not working in GTK+ apps ===
  
If the style or theme engine you setup isn't showing in your GTK apps then it's likely your GTK settings files aren't being loaded for some reason. You can check where your system expects to find these files by doing the following..
+
If the style or theme engine you set up is not showing in your GTK applications then it is likely your GTK+ settings files are not being loaded for some reason. You can check where your system expects to find these files by doing the following..
 
  $ export | grep gtk
 
  $ export | grep gtk
  
Usually the expected files should be ~/.gtkrc for GTK1, ~/.gtkrc2.0 or ~/.gtkrc2.0-kde for GTK2
+
Usually the expected files should be {{ic|~/.gtkrc}} for GTK1 and {{ic|~/.gtkrc2.0}} or {{ic|~/.gtkrc2.0-kde}} for GTK+ 2.x.
 +
 
 +
=== GTK+ apps don't use svg (breeze) icons after system upgrade ===
  
Newer versions of gtk-qt-engine use ~/.gtkrc2.0-kde and set the export variable in ~/.kde/env/gtk-qt-engine.rc.sh
+
Try to run this to fix this issue:
If you recently removed gtk-qt-engine and are trying to set a GTK theme then you must remove ~/.kde/env/gtk-qt-engine.rc.sh and reboot. Doing this will ensure that GTK looks for it's settings in the standard ~/.gtkrc2.0 instead of ~/.gtkrc2.0-kde
+
# gdk-pixbuf-query-loaders --update-cache

Revision as of 19:56, 7 February 2018

Qt and GTK+ based programs both use a different widget toolkit to render the graphical user interface. Each come with different themes, styles and icon sets by default, among other things, so the "look and feel" differ significantly. This article will help you make your Qt and GTK+ applications look similar for a more streamlined and integrated desktop experience.

Overview

To get a similar look between the toolkits, you will most likely have to modify the following:

  • Theme: The custom appearance of an application, widget set, etc. It usually consists of a style, an icon theme and a color theme.
  • Style: The graphical layout and look of the widget set.
  • Icon Theme: A set of global icons.
  • Color Theme: A set of global colors that are used in conjunction with the style.

You can choose various approaches:

  • Modify GTK+ and Qt styles separately with the tools listed below for each toolkit and aim for choosing similarly looking themes (style, colors, icons, cursors, fonts).
  • Use a special theme engine, which intermediates the modification of the other graphical toolkit to match your main toolkit.

Styles for both Qt and GTK+

There are widget style sets available for the purpose of integration, where builds are written and provided for both Qt and GTK+, all major versions included. With these, you can have one look for all applications regardless of the toolkit they had been written with.

Tip: You may want to apply user defined styles to root applications, see GTK#Theme not applied to root applications and Qt#Theme not applied to root applications.
Note: Since version 3.16, GTK+ 3 does not support non-CSS themes, hence previous solutions such as Oxygen-Gtk are no longer viable options.

Breeze

Breeze is the default Qt style of KDE Plasma. It can be installed with the breeze package for Qt5, the breeze-kde4 package for Qt4, and the breeze-gtk package for GTK+ 2 and GTK+ 3.

Once installed, you can use one of the many GTK+ configuration tools to change the GTK+ theme.

Adwaita

Adwaita is the default GNOME theme. The GTK+ 3 version is included in the gtk3 package, while the GTK+ 2 version is in gnome-themes-standard. adwaita-qt is a Qt port of the Adwaita theme. Unlike #QGtkStyle, which mimics the GTK+ 2 theme, it provides a native Qt style made to look like the GTK+ 3 Adwaita. It can be installed with the adwaita-qt4AUR and adwaita-qt5AUR packages for the Qt 4 and 5 versions, respectively.

To set the Qt style as default:

  • For Qt4, it can be enabled with Qt Configuration (qtconfig-qt4), choose adwaita under Appearance > GUI Style. Alternatively, edit the /etc/xdg/Trolltech.conf (system-wide) or ~/.config/Trolltech.conf (user-specific) file:
~/.config/Trolltech.conf
...
[Qt]
style=adwaita
...

Theme engines

A theme engine can be thought of as a thin layer API which translates themes (excluding icons) between one or more toolkits. These engines add some extra code in the process and it is arguable that this kind of a solution is not as elegant and optimal as using native styles.

QGtkStyle

Note: QGtkStyle has been removed from qt5-base 5.7.0 [1] and added to qt5-styleplugins [2]
Warning: Depending on GTK+ 2 theme, this style may cause rendering issues such as transparent fonts or inconsistent widgets.

This Qt style uses GTK+ 2 to render all components to blend in with GNOME and similar GTK+ based environments. Beginning with Qt 4.5, this style is included in Qt. It requires gtk2 to be installed and configured.

This is the default Qt4 style in Cinnamon, GNOME and Xfce, and the default Qt5 style in Cinnamon, GNOME, MATE, LXDE and Xfce. In other environments:

  • For Qt4, it can be enabled with Qt Configuration (qtconfig-qt4), choose GTK+ under Appearance > GUI Style. Alternatively, edit the /etc/xdg/Trolltech.conf (system-wide) or ~/.config/Trolltech.conf (user-specific) file:
~/.config/Trolltech.conf
...
[Qt]
style=GTK+
...

For full uniformity, make sure that the configured GTK+ theme supports both GTK+ 2 and GTK+ 3. If your preferred theme has inconsistent rendering after configuring Qt to use GTK+2, install gtk-theme-switch2 and choose a theme.

QGnomePlatform

This Qt 5 platform theme applies the appearance settings of GNOME for Qt applications. It can be installed with the qgnomeplatformAUR package or the qgnomeplatform-gitAUR package for the development version. It does not provide a Qt style itself, instead it requires a style that support both Qt and GTK+.

This platform theme is enabled automatically in GNOME since version 3.20. For other systems, it can be enabled by setting the following environment variable: QT_QPA_PLATFORMTHEME=qgnomeplatform.

Tips and tricks

KDE file dialogs for GTK+ applications

Chromium At least for chromium installing kdialog makes chromium used kde file dialog ( so `KGtk-wrapper` is not required )

Warning: Some GTK+ applications may not be compatible with KGtk-wrapper (e.g. Chromium), sometimes the wrapper makes the application crash (Firefox or Thunderbird).

kgtkAUR from the AUR is a wrapper script which uses LD_PRELOAD to force KDE file dialogs in GTK+ 2.x apps. Once installed you can run GTK+ 2.x applications with kgtk-wrapper in two ways (using GIMP in the examples):

  • Calling kgtk-wrapper directly and using the GTK+ 2.x binary as an argument:
$ /usr/bin/kgtk-wrapper gimp
  • Modifying the KDE .desktop shortcuts files you can find at /usr/share/applications/ to prefix the Exec statement with kgtk-wrapper.
e.g. with GIMP, edit the /usr/share/applications/gimp.desktop shortcut file and replace Exec=gimp-2.8 %U by Exec=kgtk-wrapper gimp-2.8 %U.

Using a GTK+ icon theme in Qt apps

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

If you are running Plasma, install kde-gtk-config and select the icon-theme under System Settings > Application Style > GTK.

If you are using GNOME, first check if dconf-editor is installed.

Then, run dconf-editor and look under org > gnome > desktop > interface for icon-theme key and change it to your preferred icon theme.

If you are not using GNOME, for example if you are running a minimal system with i3-wm, first install dconf-editor.

Then, run dconf-editor and look under org > gnome > desktop > interface for icon-theme key and change it to your preferred icon theme.

Since, you are not using GNOME, you might have to set the value of DESKTOP_SESSION in your profile. To do that execute the below code in a terminal and restart your system.

$ echo 'export DESKTOP_SESSION=gnome' >> /etc/profile

OR

Set export DESKTOP_SESSION=gnome somewhere in your ~/.xinitrc or, if you are using a Display manager in Xprofile.

Note: If the icon theme was not applied, you might want to check if the name that you entered of your preferred theme, was in the correct format. For example, if you want to apply the currently active icon theme to your QT applications, you can find the correct format of it's name with the command:
$ cat ~/.gtkrc-2.0 | grep icon-theme | cut -d= -f2

Improve subpixel rendering of GTK apps under KDE Plasma

See Font configuration#LCD filter.

Troubleshooting

Qt applications do not use QGtkStyle

Qt will not apply QGtkStyle correctly if GTK+ is using the GTK+-Qt Engine[broken link: invalid section]. Qt determines whether the GTK+-Qt Engine is in use by reading the GTK+ configuration files listed in the environmental variable GTK2_RC_FILES. If the environmental variable is not set properly, Qt assumes you are using the engine, sets QGtkStyle to use the style GTK+ style Clearlooks, and outputs an error message:

QGtkStyle cannot be used together with the GTK_Qt engine.

Another error you may get after launching qtconfig-qt4 from a shell and selecting the GTK+ style is:

QGtkStyle was unable to detect the current GTK+ theme.

According to this thread, you may simply have to install libgnomeuiAUR to solve this issue. This has the added benefit that you do not need to edit a file every time you change your theme via a graphical tool, like the one provided by xfce.

Users of Openbox and other non-GNOME environments may encounter this problem. To solve this, first add the following to your .xinitrc file:

.xinitrc
...
export GTK2_RC_FILES="$HOME/.gtkrc-2.0"
...
Note:
  • Make sure to add this line before invoking the window manager.
  • You can add multiple paths by separating them with colons.
  • Make sure to use $HOME instead of ~ as it will not properly expand to the user's home directory.

Then specify the theme you want in the ~/.gtkrc-2.0 file using a dedicated application[broken link: invalid section] or manually, by adding:

.gtkrc-2.0
...
gtk-theme-name="[name of theme]"
...

Some tools only insert the following include directive in ~/.gtkrc-2.0:

.gtkrc-2.0
...
include "/usr/share/themes/SomeTheme/gtk-2.0/gtkrc"
...

which apparently is not recognized by all versions of QGtkStyle. You can hotfix this problem by inserting the gtk-theme-name manually in your ~/.gtkrc-2.0 file like above.

Note: Style-changing applications will most probably rewrite the ~/.gtkrc-2.0 file the next time you change themes.

If these steps do not work, install gconf and run this command:

gconftool-2 --set --type string /desktop/gnome/interface/gtk_theme [name of theme]

If you further want to set the same icon and cursor theme, then you have to specify them, too.

gconftool-2 --set --type string /desktop/gnome/interface/icon_theme Faenza-Dark

This sets the icon theme to Faenza-Dark located in /usr/share/icons/Faenza-Dark. For the cursor theme you first have to set the gconf value.

gconftool-2 --set --type string /desktop/gnome/peripherals/mouse/cursor_theme Adwaita

Then you will have to create the file /usr/share/icons/default/index.theme with the following lines:

[Icon Theme]
Inherits=Adwaita

Themes not working in GTK+ apps

If the style or theme engine you set up is not showing in your GTK applications then it is likely your GTK+ settings files are not being loaded for some reason. You can check where your system expects to find these files by doing the following..

$ export | grep gtk

Usually the expected files should be ~/.gtkrc for GTK1 and ~/.gtkrc2.0 or ~/.gtkrc2.0-kde for GTK+ 2.x.

GTK+ apps don't use svg (breeze) icons after system upgrade

Try to run this to fix this issue:

# gdk-pixbuf-query-loaders --update-cache