Adding QT Colour Schemes to Kate when running Gnome (or how to get the dark mode back!)

If you’ve been running QT based applications under Gnome for long enough, it’s likely that you’ll eventually encounter issues with inconsistent theming and colour schemes when it comes to having QT and/or KDE based applications try to match or inherit parts of the Gnome / GTK theme you’re running. Note that this scenario is not specific to Gnome, and you can experience this issue and also fix it the same way on other desktop environments.

A particular example I’ve encountered occurred when moving from Fedora 32 to 33. The text editor “Kate” no longer uses a dark colour scheme if you’ve got the supplied “Adwaita-dark” applied to Gnome.

Notice how the outer GUI is white. Previously in Fedora 32 it would match the dark GUI colours used by the “Adwaita-dark” Gnome theme, however this no longer occurs in Fedora 32. Note that the inner editor’s “Colour Theme” works fine. It’s using “Solarized Dark”.

There are no issues setting a “Colour Theme” under Kate’s “Editor Component” settings – however this only applied to the inner editor. What we want is a theme we can choose under “Settings > Colour Scheme”. The only option you’ll see is “Default” – at least with Kate under Fedora 33.

We can fix this by installing Kvantum. We actually don’t even need to perform any configuration either! Simply installing it will be enough.

sudo dnf install kvantum
Whoa. We now have different “Colour Schemes” to choose from!

Now that Kvantum is installed, if you check “Settings > Colour Scheme” inside Kate, you’ll see a bunch of different options. “KvGnomeDark” will get you the same dark theme that gets inherited when running Kate under Fedora 32 using the “Adwaita-dark” Gnome theme. There are other nice options too, like “KvAdaptaDark”.

It’s worth mentioning that Kvantum has more to it than just what has been demonstrated here. Kvantum can be used to “hook” into QT applications and set specific theme/scheme options across QT applications. I’d recommend checking out these YouTube guides below.

Asus Zenbook UX431F display won’t work on Fedora 30 Linux without “NOMODESET”

Upon installing Fedora 30 to an Asus Zenbook UX431F, I encountered an issue where there is no display output unless “nomodeset” is inside the GRUB config. This limits the display resolution to 800×600 for the Zenbook’s screen which isn’t ideal. External monitors will work just fine though.

The first issue of note is that the Fedora live ISO will not output anything to the monitor when going through the normal installation process. At the boot prompt when using the live ISO you’ll need to go to Troubleshooting and Install Fedora in basic graphics mode.

Once Fedora has installed run through the following steps –

  • Download 1920×1080.bin from here or here.
  • Move that file to /lib/firmware/edid/
  • Edit /etc/default/grub and remove nomodeset then add the following line to the bottom – GRUB_CMDLINE_LINUX_DEFAULT="drm.edid_firmware=eDP-1:edid/1920x1080.bin"
  • Run sudo grub2-mkconfig -o /boot/grub2/grub.cfg
  • Reboot

Fedora should boot up and display at the proper 1920×1080 60hz resolution. After doing this there is an unfortunate issue wherein the onboard audio seems to stop working. I’m unsure as to why this is but if you use an external audio device such as a USB DAC or USB headset – audio will work fine through that. The onboard audio does work prior to this fix, however the system volume slider simply returns the volume as off or at maximum rather than incrementing properly. Edit – After a running a recent yum update I’m no longer having any issues with the onboard audio.

This issue appears to be present across most Linux distributions on some Asus Zenbook devices as tested by other users. It might also be a wider issue for devices using the Intel HD 620 integrated GPU. For further information on the actual bug and the original source of this fix, please refer to the following links –