How To Make KDE Apps Look Normal On Gnome With The Adwaita-Qt theme

Linux has a large assortment of open source applications written with a ton of different toolkits. These toolkits are often referred to by name in the community (GTK and Qt). These two frameworks look vastly different from each other, and it causes some inconsistencies within desktop themes. Over the years many have tried to solve this. On Qt-based desktop environments (like KDE Plasma) there is a theme that makes GTK/Gnome-like applications look more at home. It turns out there’s also an effort to make Qt applications look less alien on GTK desktops as well. It’s all accomplished with the Adwaita-Qt theme.

In this article, we’ll teach you how to download and install Adwaita-Qt. Additionally, we’ll go over how to apply it for Qt applications on all modern GTK Linux desktop environments.

Install Git

Start out by installing the Git package to your operating system. You’ll also need to install cmake and have the Qt framework.


sudo apt install git cmake qt5* lxqt-config


sudo apt-get install git cmake qt5* lxqt-config

Arch Linux

sudo pacman -S git cmake qt5-base lxqt-config


sudo dnf install git cmake qtbase5-common-devel qt5-qtbase-devel lxqt-config


sudo zypper install git cmake lxqt-config

sudo zypper install patterns-openSUSE-devel_qt5

Other Linuxes

The Adwaita-Qt theme on Github is uncompiled source code. As a result, it’ll run on anything with the right tools. The tools needed to compile this code are Cmake, Qt5 development libraries, and Git. Additionally, you’ll need to install the LXQt Config app, to quickly apply the theme to Qt applications.

Open up a terminal and use the package manager to search for “qt5 development”, “cmake”, “git”, and “lxqt-config”. Install these packages. If they all install successfully, you’ll be able to build the Adwaita-Qt theme correctly.

Building Adwaita-Qt

Start out the build process by using the git tool to grab the source code using clone.

git clone

Enter the newly cloned adwaita-qt folder using the CD command.

cd adwaita-qt

At this point, you’ll need to make a build folder for the Cmake builder tool. With mkdir, create the new build folder inside ~/adwaita-qt.

mkdir build

Move from adwaita-qt to the build sub-folder.

cd build

Use the Cmake tool to configure the code, and generate the building files.


Now comes the compiling part. In the terminal, run the make command.


Running make should take a while, so let the terminal be. You’ll see lots of lines go by, as the compiler puts Adwaita-Qt together. The compiler will complete when the terminal enables you to type again.

The last part of the compiling process is installation. To install Adwaita-Qt system-wide, run the install command with sudo.

sudo make install

Alternatively, install the Adwaita-Qt theme for a single user by removing sudo. Installing the theme as a single user means that the Adwaita-Qt theme needs to be re-installed for each user that needs access to it.

make install

Enabling Adwaita-Qt

Adwaita-Qt is not a GTK theme. Instead, it is Qt in nature. Since the theme is Qt and not GTK, none of the modern desktops have a way to apply it. It is because of this that earlier in the guide we installed lxqt-config. This tool is an essential part of the LXQt desktop. However, it works nearly anywhere.

Launch the LXQT-Config tool by pressing Alt + F2 and typing in lxqt-config in the prompt.

Inside the config tool, look for “Appearance” and click on it. If the Adwaita-Qt theme built correctly, it should show up in the list. Click on it to tell the system to use it as the default Qt skin.

Note: you may need to restart your PC for the changes to take full effect.

After the config tool applies the skin, launch an application on your Linux desktop that uses Qt and not GTK. Confirm it’s using the correct theme. If the theme fails to apply, go back to lxqt-config and try again.

Disable The Theme

Adwaita-Qt does an excellent job at making Qt applications look less out of place on desktop environments like Gnome Shell, Cinnamon, etc. Still, if you’re not a huge fan of this theme, it’s understandable. Not many people choose to stick with the Adwaita theme in favor of a custom one. If you’d like to disable the theme, it’s as easy as going back into lxqt-config.

Once inside, select the “Appearance” button, just like last time. To disable the theme, select a different one (that isn’t Adwaita-Qt) to “disable it.” Then, open up a terminal and delete the source-code from your home folder.

rm -rf ~/adwaita-qt

After switching off the theme in lxqt-config, Qt applications should no longer be using Adwaita-Qt.

Read How To Make KDE Apps Look Normal On Gnome With The Adwaita-Qt theme by Derrik Diener on AddictiveTips – Tech tips to make you smarter

How To Configure Razer Gaming Peripherals On Linux With Polychromatic

Do you have Razer gaming hardware? Confused as to how to configure Razer gaming peripherals on Linux computer? If so, you may be interested in the Polychromatic tool. It’s a complete graphical front-end tool for Linux that can configure Razer gaming peripherals.

To install the Polychromatic tool, you need to be running the latest Razer device drivers on Linux. Follow the instructions below to learn how to get them working.

Install OpenRazer And Polychromatic

The OpenRazer driver has lots of support on Linux. No matter what Linux distribution you’re running, there’s probably a way to install it. To get started, open up a terminal window and enter the commands that correspond to your operating system.


Like most third-party software, OpenRazer  can be installed on Ubuntu via a PPA. In the terminal window, use the add-apt-repository command to add the software source.

sudo add-apt-repository ppa:openrazer/stable

Next, you’ll need to refresh Ubuntu’s software sources. Running a refresh is critical, otherwise, Ubuntu won’t see the new PPA.

sudo apt update

After updating, you’ll notice that apt says there are updates available. Install them with the upgrade command. Don’t skip this step, as it is essential. Without installing critical updates, Ubuntu may not run Razer software as well as it could.

sudo apt upgrade -y

Now that everything is up to date use the apt install command to grab the latest version of the OpenRazer drivers.

sudo apt install openrazer-meta

Seeing errors when trying to install OpenRazer? This error may be due to the Universe software source being disabled. Enable it with the following command:

sudo add-apt-repository universe

sudo apt update

After the update finishes, try to re-install OpenRazer with the command above.


Like Ubuntu, the software can be installed via third-party software sources. Unfortunately, PPAs and Debian don’t go very well together, so you’ll need to do it the old-fashioned way.

First, use the echo command to add OpenRazer to Debian’s sources.list file.

Note: be sure to do this as root with su, or add yourself to the sudoer file.


echo 'deb /' > /etc/apt/sources.list.d/hardware:razer.list

The OpenRazer software source is now in Debian. Next, it’s time to run the update command, so that the new software source is accessible.

sudo apt-get update

Running apt-get update sometimes shows updates that are ready to install. Be sure to install the updates so that OpenRazer runs at it’s best.

sudo apt-get upgrade

Lastly, install the driver with:

sudo apt-get install openrazer-meta

With the new OpenRazer drivers working, finish everything up by installing Polychromatic:

echo "deb xenial main" | sudo tee -a /etc/apt/sources.list.d/polychromatic.list
sudo apt-key adv --recv-key --keyserver 96B9CD7C22E2C8C5
sudo apt-get update
sudo apt-get install polychromatic

Arch Linux

OpenRazer is available to all Arch Linux users via the Arch Linux user repository. To install this software from the AUR, install the Git package using the Pacman packaging tool.

sudo pacman -S git

It may also be necessary to install the base-devel package too (required for interacting with the AUR).

sudo pacman -S base-devel

Next, use the git command to pull the latest pkgbuild file of OpenRazer.

git clone

CD into the clone folder and start the build process with makepkg. Understand that building from the AUR is touchy. Usually, using the -si flags install all dependencies automatically. However, sometimes, this fails. In this event, please visit the OpenRazer page on the AUR and install all dependent programs manually.

With OpenRazer installed, move on to installing the Polychromatic app.

git clone

cd polychromatic

makepkg -si


Installing OpenRazer and PolyChromatic on Fedora is possible thanks to the Suse OBS. Start off adding the software source for OpenRazer in the terminal. In this guide, we’ll focus on Fedora 28. However, there are software repositories available for Fedora 27 and 26. Replace “Fedora 28” with your release in the commands below.

sudo dnf config-manager --add-repo

After adding the OpenRazer software source, add the Polychromatic one too.

sudo dnf config-manager --add-repo

Finally, install both Openrazer and Polychromatic:

sudo dnf install openrazer-meta polychromatic


To install the Polychromatic tool on OpenSUSE, and add both the OpenRazer and Polychromatic software sources to the system.

sudo zypper addrepo


sudo zypper addrepo

Update the software sources for Zypper with the refresh tool.

sudo zypper refresh

Finally, install OpenRazer and Polychromatic using zypper install.

sudo zypper install polychromatic openrazer-meta

Using Polychromatic

If you need to change the RGB lighting on your Razer device, start off by opening the Polychromatic tool. As it opens up, you should instantly see options available for several different types of supported devices. Provided that the OpenRazer driver is working, you should be able to easily edit these settings.

Select “overview” to show the Razer devices connected and recognized by your Linux PC. Polychromatic will only let you modify Razer devices that are connected to the system.

To modify a Razer device, select the device name in the options menu to open its settings window.

Inside the settings window, use Polychromatic to modify lighting settings, change options, and etc. Changing settings should automatically apply to the device.

Read How To Configure Razer Gaming Peripherals On Linux With Polychromatic by Derrik Diener on AddictiveTips – Tech tips to make you smarter

How To Create Custom Battery Alerts For A Linux Laptop

The battery system for most desktop environments on Linux is pretty straightforward. It’ll send you a message when your laptop is charging, when the battery is about to die, and when the battery is done charging. For average users, this probably seems like it’s good enough. However, if you like to track your laptop’s battery life and track how much power you’re using, you’ll need something a little more robust. Introducing Battery Monitor: a Python 3 based application that allows users to create custom battery alerts. To use Battery Monitor, you need to be running Ubuntu, Debian or have the ability to compile the source code and run it.


The developer behind the Battery Monitor tool is primarily targeting Ubuntu. Since Ubuntu is the primary OS for this software, users will have no trouble installing it. To get it working, first, add the PPA archive.

Note: Ubuntu 18.04 doesn’t appear to have support for Battery Monitory yet. Previous releases, however, work fine.

sudo add-apt-repository ppa:maateen/battery-monitor

Just adding the PPA to the system doesn’t mean that Battery Monitor is installed. First, you must refresh the Ubuntu software sources.

sudo apt update

Running the apt update tool usually will show software upgrades for Ubuntu. Please install these new software upgrades, as Battery Monitor may need them. Upgrades can easily be installed by running the apt upgrade command.

sudo apt upgrade -y

With the PPA working and everything up to date, Battery Monitor is ready for installation. To install, run this command:

sudo apt install battery-monitor

If you want to uninstall Battery Monitor, run:

sudo apt remove battery-monitor -y


Battery Monitor works on Debian, though the developer hasn’t explicitly said so. Specifically, the Ubuntu 16.04 Xenial package seems to work just fine. To install Battery Monitor, first, use wget to download the Debian package file.

Note: Battery monitor runs well on Debian Stable. Use at your own risk on Unstable and Testing.


Use the dpkg app to install Battery Monitor.

sudo dpkg -i battery-monitor_0.5.4-xenial_all.deb

Using the dpkg command to install an Ubuntu program on Debian is iffy. In this case, it is because the dependencies don’t automatically resolve. Luckily, it’s easy to solve this issue. To correct the dependency errors, run the apt install -f command.

sudo apt install -f

After apt install -f finishes fixing dependency issues; Battery Monitory should work just fine.

Install From Source

If you’re not an Ubuntu or Debian user but still want to use the Battery Monitor tool, you’ll have to resort to compiling everything from source. Start off by installing the Git package. This package will allow you to download and interact with code from Git-based sites.

Operating system not listed? Just search your package management tool for “Git” and install it!

Note: to run this software; you’ll need to install the correct dependency files.

Arch Linux

sudo pacman -S git


sudo dnf install git


sudo zypper install git

Using Git, grab the latest Battery Monitor source code.

git clone

CD into the newly cloned source folder.

cd battery-monitor

In the source directory, run make to compile Battery Monitor.

sudo make install

When the compilation finishes, Battery Monitor should be ready to go!

Using Battery Monitor

When you install Battery Monitor, you’ll notice there are two options in the application menu. Specifically, you’ll see that there is a “Battery Monitor” and “Battery Monitor GUI” launch option. To start using the tool, launch “Battery Monitor.” This launch option opens up the monitor tool and runs it in the background.

Once Battery Monitor is running, start up the GUI tool to edit the settings.

Battery Monitor has several settings that the user can edit for their uses. By default, Battery Monitor only has two warning notifications set up. These warnings go off when the program determines your battery life is at 10% and 30%.

Want more frequent warnings? Look for “First custom warning at,” “Second custom warning at,” and “Third custom warning at.” Next to each of these text boxes, write out a number corresponding to battery percentage.

For example, if you’d like to have Battery Monitor let you know when your laptop is about halfway dead, write “50” in one of the custom notification slots.

To get the most out of Battery Monitor, we recommend following this setup for custom warnings.

First, change “low battery warning” from 30 to 20. Next, add 50 as one of the custom warning notifications (so that you’ll see a warning when your battery is 50% drained). After setting the 50% number, add  75 to another custom slot. This change will allow Battery Monitor to let you know when 25% is drained from your laptop.

Finally, change “very low battery” from 10 to 8. With these settings, you’re sure to get the most out of Battery Monitor. When you’re happy with the settings, click the “Save” button to apply the new changes instantly.

If you want custom battery alerts on Windows, check out this post that shows you how you can create them easily.

Read How To Create Custom Battery Alerts For A Linux Laptop by Derrik Diener on AddictiveTips – Tech tips to make you smarter

How To Install Flowblade Video Editor For Linux

There is no shortage of advanced video editing tools on Linux. In fact, there are excellent choices out there like Kdenlive, Avidemux, etc. However, for as good as all these applications are, they don’t try to target serious video editors. Instead, they strive to offer up a competent, open-source alternative video editor. There’s nothing wrong with that. Still, if these editing tools don’t meet the mark, it may be worth giving this Flowblade video editor a shot.

Flowblade is a robust, non-linear video editing application for the Linux desktop. It’s filled to the brim with a ton of advanced features. Best of all, the app explicitly targets film editors by including features and an interface that most people are comfortable with.

Install Flowblade Video Editor


The Flowblade video editor is readily available for Ubuntu users via the Ubuntu software sources. No additional PPAs or downloadable files are required. Just open up a terminal and enter the following command:

sudo apt install flowblade


Debian users will be able to install the Flowblade video editor with a simple command.

sudo apt install flowblade

Due to the nature of how Debian works, users may be unhappy with how far behind the version of Flowblade is. If you’re looking to get the absolute latest features, it’s a good idea to download the Debian package file from the website and install that instead.

To get the latest Debian package of Flowblade, go to the official release page. Once you’ve got the file downloaded, open up a terminal window and use the CD command to move the terminal to the ~/Downloads directory.

cd ~/Downloads

Inside the ~/Downloads folder, use the dpkg command to install the latest version of Flowblade.

sudo dpkg -i flowblade-*_all.deb

Please understand that if you already have the older version installed (via the command above), the new Flowblade package will be treated as an update. If you don’t want it to be treated like an update, follow this process.

sudo apt remove flowblade --purge

Then, run dpkg to install the package version, as usual.

sudo dpkg -i flowblade-*_all.deb

Arch Linux

Arch Linux has support for Flowblade via the Arch Linux User Repository. To get started installing this software on Arch, you’ll first need to use the Pacman packaging tool to install the latest version of the Git tool. Git is required to interact with the AUR (without the help of an AUR wrapper), as well as source code, etc.

sudo pacman -S git

With the Git tool on your Arch PC, use it to grab the latest pkgbuild of the Flowblade video editor.

git clone

Move the terminal window to the newly cloned flowblade folder.

cd flowblade

Inside the Flowblade folder, you’ll need to start the package generation process. Keep in mind that Flowblade will build from source, and may take a while. Usually, when running the makepkg command, the dependencies are taken care of automatically. However, sometimes this fails (generally if the dependencies the package needs are only available in an AUR package).

If for some reason you need to install dependencies manually, visit the Flowblade AUR page and scroll down to “dependencies.”

Build and install Flowblade for Arch Linux with:

makepkg -si


Getting Flowblade on Fedora first requires the RPM Fusion software repository. To add it, download the RPM with DNF.

Note: change X to fit your version of Fedora.

sudo dnf install

With RPM Fusion on Fedora, it’s safe to get Flowblade.

sudo dnf install flowblade


OpenSUSE can run the Flowblade video editor, but to install it, users will need to enable a third-party software source. Using Zypper, add the Packman repo:

Leap 42.3

sudo zypper addrepo packman


sudo zypper addrepo packman

Refresh Suse’s software repositories, and install Flowblade.

sudo zypper ref

sudo zypper install flowblade


If your Linux operating system isn’t in the list of installation instructions, there may be a chance that your Linux distribution doesn’t support Flowblade with an installable binary. If this is the case, the best alternative is to go the Flatpak route instead. Using Flatpak is excellent, as it’s on virtually every Linux distribution. As long as you can install Gnome, you’ll probably be able to use Flatpak technology.

To use the Flatpak version of the Flowblade video editor, you’ll first need to enable the Flatpak technology on your Linux distribution. Check out our guide here and learn how to set it up. When it’s working, open up a terminal window and use the command below to install the Flowblade video editor.

First, add the Flathub software repository to your Flatpak. Adding this source is essential, as Flowblade is only installable from Flathub.

sudo flatpak remote-add --if-not-exists flathub

Now that the Flathub software source is enabled, you’ll be able to install the Flowblade video editor.

sudo flatpak install --from -y

Note: add -y to the end of the installation command to avoid having to select “yes” during installation.

Read How To Install Flowblade Video Editor For Linux by Derrik Diener on AddictiveTips – Tech tips to make you smarter

How To Easily Search Clipboard History On Linux With Indicator Bulletin

Having a clipboard is one of the most underappreciated things about modern operating systems. With it, anyone can copy information from one place, store it for a short time and transfer it somewhere else. Still, for as amazing as clipboards are, there are lots of improvements needed for it to be perfect e.g., the ability to save more than one item, or a way to search clipboard history.

That’s where Indicator Bulletin comes in. The primary goal of this tool is to improve the clipboard on Linux and make it so that what users save in the clipboard doesn’t get lost.

Note: to use Indicator Bulletin you’ll need to have Ubuntu, Debian or the ability to download the source code and run it using Git.


Installating Indicator Bulletin is quite easy for Ubuntu users as it’s distributed via a PPA. To enable this software source, enter the following command:

Note: Ubuntu 18.04 doesn’t appear to have support for this PPA yet. However, all other versions of Ubuntu seem to be working fine.

sudo add-apt-repository ppa:1047481448-2/sergkolo

Now that the Sergkolo PPA is on Ubuntu, you’ll need to run the update command to refresh Ubuntu’s software sources.

sudo apt update

Usually, running the update command lets the user know of any software updates that need to be installed. If you see notifications for pending upgrades, please install them before continuing with the install process.

sudo apt upgrade -y

Finally, install the Indicator Bulletin app with:

sudo apt install indicator-bulletin

Need to uninstall the software? Run apt remove.

sudo apt remove indicator-bulletin --purge


Debian users should have no issue running the Indicator Bulletin software once it’s installed. Unfortunately, there is no dedicated software repository to use. Since Debian and Ubuntu PPA’s don’t work well together, the best bet Debian fans will have is to download a package file.

In this guide, we’ve tested the Ubuntu 16.04 (Xeinal) package and found it to work flawlessly on Debian Stable 9.4. We have not tested it on Unstable and Testing. To get the package, download it from Launchpad using the wget tool.


Be sure to rename the package file to something more comfortable to write in terminal:

mv indicator-bulletin_0.1-0~201703080331~ubuntu16.04.1_all.deb indicator-bulletin.deb

With all that taken care of, it’s time to start installing the software. In the terminal prompt, use the dpkg command to tell Debian to install Indicator Bulletin.

sudo dpkg -i indicator-bulletin.deb

During the installation of Indicator Bulletin, some dependency irregularities may occur. To fix it, run the apt install -f command.

sudo apt install -f

Other Linuxes Via Source Code

Usually, most of the mainstream Linux distributions will have packages available for installation. Sadly, for whatever reason, Indicator Bulletin only has easy installation instructions out there for Ubuntu and Debian.

If you’re looking to run this software on Arch Linux, Fedora, OpenSUSE, etc., you’ll need to download the code from Github instead. To start off, install the Git package.

If your operating system isn’t listed below, install Git by searching for “git” in your OS’s package management tool.

Note: the developer doesn’t outline any required dependencies for Indicator Bulletin. Use at your own risk!

Arch Linux

sudo pacman -S git


sudo dnf install git


sudo zypper install git

With Git installed, use it to download the latest source code for Indicator Bulletin and place it on your PC.

git clone

No compiling of this software is required. Instead, it should be straightforward to run the program directly. To start Indicator Bulletin, open up a terminal window and CD into the source code folder.

cd ~/indicator-bulletin

Using Chmod, update the permissions of the files.

sudo chmod +x *

Next, move the shortcut file to the Desktop (for easy launching).

mv indicator-bulletin.desktop ~/Desktop

Additionally, make a copy of the Desktop file and place it in ~/.config/autostart, if you’d like it to auto-launch when you log in.

cp ~/Desktop/indicator-bulletin.desktop ~/.config/autostart/

Using Indicator Bulletin

Start Indicator Bulletin. As it starts up, it should instantly start accessing and saving anything you’ve had in your clipboard.

To use, find a piece of text, click anywhere, and click “copy.” Once the “copy” option is selected, the text will instantly appear in Indicator Bulletin. From here, you’ll be able to see it in the app.

Pinning Items

Indicator Bulletin lets users favorite, or “pin” items in the clipboard history for quick access. If you’ve saved something with the app that you want easy access to, find it in the list and hover on it to show the settings menu. After that, select “add to pinned.”

When pinned, the item will be visible in the “pinned” menu.

Search Clipboard

One of the benefits of having an enhanced clipboard is a search function. If you saved something to Indicator Bulletin for later but can’t find it, and don’t want to scroll through dozens of items, click the “find text option.”

Inside the “find text” menu, enter a search term, and the clipboard item you want should appear!

Read How To Easily Search Clipboard History On Linux With Indicator Bulletin by Derrik Diener on AddictiveTips – Tech tips to make you smarter