Show Live Scores in Ubuntu Panel for NBA, EPL, or Other Sports Teams

For sports fans who want to keep a watchful eye on live scores for favorite teams, here’s an indicator applet for Ubuntu, Fedora, and other Linux with GNOME.

It’s colosseum, which displays an indicator in top-panel system tray area. By clicking on it will show the menu with live scores for your favorite sports teams.

So far, it supports 12 sports leagues:

  • Bundesliga
  • 2. Bundesliga
  • English Premier League
  • La Liga
  • Ligue 1
  • Major League Baseball
  • National Basketball Association
  • National Football League
  • National Hockey League
  • Serie A
  • UEFA Champions League
  • Women’s National Basketball Association

There are also 5 supported tournaments, including

  • CONCACAF Gold Cup
  • Copa America
  • FIFA World Cup
  • UEFA Champions League
  • UEFA European Championship

How to Install this live scores indicator

This indicator is available as an extension, which so far supports GNOME v40, 41, 42 and 43. Meaning, you can install and use it in Ubuntu 22.04+, Fedora 35+, Arch, Manjaro, Rocky Linux, etc with GNOME desktop.

1. For Ubuntu 22.04 and higher, first search for and install “Extension Manager” from Ubuntu Software.

Install Extension Manager in Ubuntu 22.04+

2. Then open the extension manager tool, navigate to “Browse” tab. Finally, search and install “colosseum” extension.

3. Once installed, switch back to “Installed” tab, and click on gear icon for that extension to open the configuration page.

There, set the refresh time interval, turn on the toggle buttons for your favorite sports leagues and/or tournaments. New configuration tabs will appear, where you can follow your favorite teams.

TIP: If the indicator applet does not appear in panel, try to turn off and then turn on again the extension, or just log out and log back to restart Gnome Shell.

For other Linux, go to this page and use ON/OFF switch to install the extension. And, install and use “Gnome Extensions” app to manager extensions’ configurations.

How to Hide App Shortcut Icon in Ubuntu 22.04 | 20.04 & Other Linux

Got an application, but you want to make it in-visible from start menu, app grid, app launcher search result, and dock launcher?

It’s easy to do the trick by adding rule NoDisplay=true or Hidden=true into the ‘.desktop’ file for that application. And, here’s how to do it step by step.

Hide Shortcut Icon for native Deb/RPM & Snap apps

For applications installed as the native .deb (or .rpm for RPM based systems), and Snap packages, the ‘.desktop’ files are usually stored in /usr/share/applications directory.

1. First, open terminal either from start menu or by pressing Ctrl+Alt+T on keyboard in Ubuntu. When it opens, run command to navigate to that folder:

cd /usr/share/applications/

2. Then, find out the .desktop file by either listing all of them via ls command. Or, filter via:

ls | grep 'keyword_here'

3. Once you find out the .desktop file for your applications, edit it via command:

sudo gedit your_application.desktop

Replace gedit with your system text editor, or use nano command line editor that works in most Linux.

4. Finally, add (or change value if the key already exist) the line below:


Finally, save the file. For nano text editor, press Ctrl+X, type y and hit Enter.

In next time you logging into the system, the app shortcut will no longer exist in start menu, app grid, the left/bottom dock, and ‘Activities’ overview search result.

Hide Shortcut Icon for Flatpak Apps

For the universal Flatpak applications, the ‘.desktop’ files are located in ‘/var/lib/flatpak/exports/share/applications/‘ directory.

1. So, first open terminal and run command to navigate to that folder:

cd /var/lib/flatpak/exports/share/applications/

2. Use ls or ls |grep 'keyword' to find out the file.

3. Finally, edit it either via Gedit or other text editor:

sudo gedit your_application.desktop

Add the NoDisplay=true line and save the file. Also, log out and back in to see result.

Copy & paste the .desktop file into local folder

The previous change may be overridden after updating the software package. As a workaround, you may copy & paste the .desktop file into local folder and then do the change. Your system will always take use of the local one.

For native package and Snap, open terminal and run command to copy the file:

sudo cp /usr/share/applications/your_app.desktop ~/.local/share/applications/

Then, navigate to local directory, change the ownership, and finally edit the file:

cd ~/.local/share/applications/ && sudo chown $USER:$USER your_app.desktop && gedit your_app.desktop

For Flatpak applications, the local folder is “~/.local/share/flatpak/exports/share/applications/“. So, do the commands below instead:

sudo cp /var/lib/flatpak/exports/share/applications/your_app.desktop ~/.local/share/flatpak/exports/share/applications/
cd ~/.local/share/flatpak/exports/share/applications/ && sudo chown $USER:$USER your_app.desktop && gedit your_app.desktop

How to Use SIGINT and Other Termination Signals in Linux

How to Use SIGINT and Other Termination Signals in Linux

You must be used to use Ctrl + C for terminating any process, but do you know it sends the SIGINT signal?

But there are more types of terminating signals than just using SIGINT (cough Ctrl + c cough). So let’s dive deep into the ocean of terminating signals!!

Use Termination  Signals in Linux

The kill command is what users generally use for termination but do you know that 50+ signals kill command avails you?

How to Use SIGINT and Other Termination Signals in Linux

This means you can use those numbers instead of writing the signal name.

For example, if you want to stop execution, you’re most likely to use SIGTSTP like this:

kill -SIGTSTP %jobID
How to Use SIGINT and Other Termination Signals in Linux

Similarly, you can use 20 as it is associated with SIGTSTP to have the same effect:

kill -20 %jobID
How to Use SIGINT and Other Termination Signals in Linux

But there are too many options so I’m going to cover widely used ones.

So let’s start with the SIGSTOP.

Terminate processes using SIGTSTP

First, let me start with the killing foreground process.

It is quite simple compared to killing background processes as you just have to use keybindings accordingly.

The keybinding of executing SIGTSTOP is ctrl + z. For example, I’ll be using the sleep command:

sleep 15000
How to Use SIGINT and Other Termination Signals in Linux

Here you can see I’ve used the jobs command, a helpful utility that shows running and recently terminated processes.

But what about background processes? Well, there you’d need to use the kill command specifying PID or JOB ID with -SIGTSTOP.

kill -SIGSTP %jobID
How to Use SIGINT and Other Termination Signals in Linux

Use SIGCONT to resume command execution

There are times when you want to resume the command execution that you terminated recently and in those cases, -SIGCONT will help you.

For this example, I’ll be using the previously terminated process and then use the given command to resume its execution:

kill -SIGCONT %jobID
How to Use SIGINT and Other Termination Signals in Linux

Terminate execution using SIGINT

This is my all-time favorite command, as whenever I find myself stuck somewhere, ctrl + c makes wonders for me.

And if you’re not aware of this, let me show you how it can terminate command executions with ease:

How to Use SIGINT and Other Termination Signals in Linux

But the problem with SIGINT is it may not work in some places such as bash interpreters.

For example, here’s a bash script that takes input from the user:


trap date SIGINT

read input
echo User input: $input
echo Exiting now
How to Use SIGINT and Other Termination Signals in Linux

As you can see, it gave me the current date and time when I pressed ctrl + c and only stopped when it got input from my side.

I know this script was created in that way but you got my point right. You can not rely on SIGINT always.

Use SIGQUIT for termination

The SIGQUIT is similar to SIGINT but it also generates a core dump before execution.

In simple words, the core dump is a file that is generated automatically before the system crashes or the process is terminated.

Also, It can be provoked by using ctrl + . So you can use it for terminating foreground and background processes.

So let me show you how it behaves when you only try ctrl + :

How to Use SIGINT and Other Termination Signals in Linux

But how to use it for terminating background processes? Let me bring light to the syntax part to make it easier:

kill -SIGQUIT %jobID
How to Use SIGINT and Other Termination Signals in Linux

Terminate executions using SIGTERM

As its name suggests, this is a termination signal that terminates the program but unlike SIGKILL (that kills the program no matter what), this is a polite way of asking the program to be terminated.

If you want to learn more about SIGTERM vs SIGKILL, I’d recommend the other guide that touches on the core fundamentals:

What is SIGTERM? What’s the difference between SIGKILL & SIGTERM?
Both SIGTERM and SIGKILL are used for killing a process in Linux. But you should prefer using SIGTERM. Here’s why!
How to Use SIGINT and Other Termination Signals in Linux

One thing to remember is that sometimes it performs cleanups before proceeding with termination.

So the syntax of SIGTERM is quite simple:

kill -SIGTERM %jobID
How to Use SIGINT and Other Termination Signals in Linux

Use SIGKILL (the last resort)

It is always advised to use SIGKILL as a last resort because it will kill any child process immediately making it the most brutal way of killing processes!

Once in a while, I found myself in a situation where some programs won’t work at all and they can’t be terminated at all!

So in those cases, I use SIGKILL to give that process the most unpleasant death.

Now, let’s have a look at the generic syntax of SIGKILL:

kill -SIGKILL %jobID
How to Use SIGINT and Other Termination Signals in Linux

Wrapping Up

This guide was a basic explanation of how you can use varieties of signal options to terminate executions. And if you still have any doubts, let me know in the comments.

How to Know if You Are Using Systemd or Some Other Init in Linux

How to Know if You Are Using Systemd or Some Other Init in Linux

When you start a Linux system, it starts with only one process, a program called init.

Since the launch of UNIX version five (System V), the SysV init system has been the most popular and it made to the Linux systems in 1991.

It remained the most popular init system for years but gradually, many Linux distributions started using OpenRC, Runit, UpStart etc.

At present, systemd is widely used and thus you are likely to be using systemd on your system.

But how do you confirm it? You run this command:

ps -p 1 -o comm=

If you get systemd in the output, you are using systemd.

How to Know if You Are Using Systemd or Some Other Init in Linux
An Ubuntu system running systemd

That works for Linux distributions using systemd but what if you are using some other init system? Let’s discuss that part as well

Checking the init system in Linux

Remember that the init is the first process to start in your Linux system.

This means that the detail lies in the process with PID 1. Check the process 1 then:

ps 1

But unfortunately, that’s not enough because the the process if often showed as /sbin/init and that doesn’t give accurate information.

abhishek@LHB:~$ ps 1
      1 ?        Ss     0:01 /sbin/init splash

The /sbin/init is a symbolic link to the actual init process. You can follow the symbolic link and see real process.

I am using the stat command and you can see that /sbin/init is linked to /lib/systemd/systemd in Ubuntu.

abhishek@LHB:~$ stat /sbin/init
  File: /sbin/init -> /lib/systemd/systemd
  Size: 20        	Blocks: 0          IO Block: 4096   symbolic link
Device: 10306h/66310d	Inode: 30675721    Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2022-09-21 09:17:59.616364311 +0530
Modify: 2022-06-27 23:58:46.000000000 +0530
Change: 2022-07-12 18:24:23.667196373 +0530
 Birth: 2022-07-12 18:24:23.667196373 +0530

This is an indication that systemd is in use.

How to Know if You Are Using Systemd or Some Other Init in Linux

Take another example. I am using Alpine Linux version 3.16. Here’s the init information.

localhost:~# stat /sbin/init
  File: '/sbin/init' -> '/bin/busybox'
  Size: 12        	Blocks: 0          IO Block: 4096   symbolic link
Device: 800h/2048d	Inode: 169         Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2022-09-22 04:53:46.677137693 +0000
Modify: 2022-07-21 04:10:19.149395174 +0000
Change: 2022-07-21 04:10:19.149395174 +0000

As you can see, Alpine Linux is using the lightweight BusyBox init system.

How to Know if You Are Using Systemd or Some Other Init in Linux

You may also use the pstree command but that may not work in every other distribution to identify the init system.


For Ubuntu, it clearly indicates if the Linux distro is using systemd.

How to Know if You Are Using Systemd or Some Other Init in Linux

As you can see, it might not be straightforward but it’s not that complicated as well to know whether your Linux system is using systemd or not.

Enable Thumbnails for EPub / MOBI Files in Ubuntu 22.04 | 20.04 & Other Linux

Got some ePub and/or MOBI books in your PC? Debian / Ubuntu has recently includes a package in their repository for generating thumbnails for these files.

As you may know, Linux Mint 21 was released recently with a thumbnail generators for AppImage, ePub, MP3 and RAW files. Debian/Ubuntu now has similar tool called gnome-epub-thumbnailer, though it’s only for ePub and MOBI books.

With the package installed, the default file manager will no longer display the universal “e” image with green background for all ePub files. Instead, it shows thumbnail book covers.

Don’t know if Ubuntu 22.10 will come with it out-of-the-box, since it’s not released yet. But, user may manually install the package by running the apt command below in terminal.

Open terminal (Ctrl+Alt+T) and run command to install gnome-epub-thumbnailer in Ubuntu 22.10 or Debian Unstable:

sudo apt update && sudo apt install gnome-epub-thumbnailer

NOTE: the package is only for the default GNOME Desktop! Install the Foliate eBook reader from system repository will also install it as recommend dependency package.

Enable EPub / MOBI Thumbnails in Ubuntu 22.04 | 20.04

The package is not available in the current LTS releases. Ubuntu 22.04 user can however download the .deb package directly from the build page:

Click the little triangle for Ubuntu 22.10 (Kinetic Kudu) build to expand, and select download the amd64.deb for modern PC/laptop, arm64/armhf for ARM, or other format depends on your devices.

Finally, double click to open the .deb package via “Software Install” (Ubuntu Software) and install it.

For Ubuntu 20.04 user, I’ve upload the package into this unofficial PPA for 64-bit (amd64) computers support.

To add the PPA and install the package, press Ctrl + Alt +T on keyboard to open terminal and run 3 commands one by one:

sudo add-apt-repository ppa:ubuntuhandbook1/apps
sudo apt update
sudo apt install gnome-epub-thumbnailer

NOTE: The first command will asks for password authentication, though there’s no asterisk feedback. Just type in mind and hit Enter to continue.

Enable EPub / MOBI Thumbnails in Fedora, Arch, SUSE Linux

Most other recent Linux systems have also added the package into their official repositories. If you want to get it, open terminal and run command:

  • For Fedora, use command:
    sudo dnf install gnome-epub-thumbnailer
  • Arch and Manjaro Linux can install it via:
    sudo pacman -S gnome-epub-thumbnailer
  • And, openSUSE user may run command:
    sudo zypper install gnome-epub-thumbnailer

Uninstall the Thumbnails

Thumbnails generate automatically once you installed the package. If somehow you want to get rid of them, open terminal and run command:

sudo apt remove gnome-epub-thumbnailer

Replace apt depends your system. For Arch, use sudo pacman -R gnome-epub-thumbnailer.

Removing the package won’t clear existing thumbnail images, until you removed the content under “~/.cache/thumbnails” either from file manager or by running command:

rm -R ~/.cache/thumbnails/*

Krita Lime PPA Abandoned! Here’re other choices to install it in Ubuntu

For users of Krita digital painting software, there’s a bad news that the Krita Lime PPA is abandoned. The repository page is even removed!

Krita Lime PPA was the ‘official’ (definitely not, but maintained by volunteer) package source in Krita’s website until the app switching to AppImage. It maintained the most recent packages for Ubuntu users who are sticking to the native .deb package.

The PPA recently announced the deprecation note: “The Krita Lime PPA has been deprecated. Please use official AppImage packages from the official Krita site instead“, and completely removed the PPA page.

How to Remove Krita Lime PPA:

If you still have the PPA in your system, you may remove it either by using “Software & Updates” utility under “Other Software” tab.

Remove PPAs via Software & Updates tool

Or, press Ctrl+Alt+T on keyboard to open terminal, and run command:

sudo add-apt-repository --remove ppa:kritalime/ppa

In case the previous methods do not work, you can manually remove the source and key files by running command in terminal:

sudo rm /etc/apt/sources.list.d/*kritalime* /etc/apt/trusted.gpg.d/*kritalime*

And finally update package cache via sudo apt update command.

Get most recent Krita package via other methods:

There are a few other choices to install or update the software package. Choose one of them that you prefer.

Option 1: AppImage

Krita website now provides the latest package for Linux via AppImage package.

It’s a single non-install executable package. Like some exe/msi for MS Windows, user can simply double-click to run the package to launch software. Though, AppImage runs in sandbox.

First, go to the software website via the link below and click download the AppImage package:

Once you got the package, right-click on it and select “Properties” and enable “Allow execute file as program” checkbox under Permissions tab. Finally, click run the package to launch Krita.

Tip: Ubuntu 22.04 does not support AppImage out-of-the-box, run sudo apt install libfuse2 in terminal to enable it.

Option 2: Flatpak

Flatpak is another package format works on most Linux and runs in sandbox. Krita website also refers to this package, though it’s maintained by the community.

The downside of Flatpak package could be that a small app can require quite a few hundreds MB downloads for run-time libraries.

1. First, open terminal (Ctrl+Alt+T) and run command to install the daemon package:

sudo apt install flatpak

2. Next, add the Flathub repository which hosts the package:

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

3. Finally, install Krita as Flatpak using command:

flatpak install flathub org.kde.krita

After installing the package, user may try to update it at any time by running command:

flatpak update org.kde.krita

(Optional) To remove the Flatpak package, use command:

flatpak uninstall --delete-data org.kde.krita

And clean up useless runtime libraries via flatpak uninstall --unused

Option 3: Other Ubuntu PPAs

If you insisting on using the native .deb package, keep an eye on the 2 others PPAs below:

  • KUbuntu Backports PPA – It’s one of official KUbuntu PPAs that contains Plasma desktop, KDE apps, which also updates Krita packages.
  • UbuntuStudio PPA – It’s the official PPA for Ubuntu Studio contains most recent Krita along with other app packages for recent LTS (meaning Ubuntu 22.04).

NOTE: Both of the PPAs do not update as soon as a new release is out, but build packages once in a while.