Graphics Archives • Page 2 of 4 • Linux Tips

How To Tell If You’re Using Wayland Or X11

Today’s article will be an interesting one, for at least a subset of readers, as we learn how to tell if you’re using Wayland or X11. The command isn’t all that difficult and is just a single command that should work with everything, but the topic might confuse some of you.

Frankly, if you ask this question to the majority of users, you’re probably going to find out that they’re still using X11. The move to Wayland has been a process, that started back in 2008. The goal is to replace X and provide a much better set of protocols.

That’s what Wayland is… It’s a set of protocols dealing with how things are displayed on your monitor. X is also a set of protocols for the display server – and it dates back to 1984. Without X (or something else), we’d have been staring at nothing but terminal outputs this entire time, so it is kind of a big deal.

That doesn’t mean the current X implementation is that old on your device, it just means that it has been the default for a long time. The upstart, that is Wayland, is meant to take care of a variety of flaws – including potential security flaws. That’d be a subject way too deep to get into today.

Currently, some distros are confident with Wayland and release distros that default to Wayland. Some offer it as an option, without it being the default. The GNOME and KDE desktop environments are currently the closest to being ‘Wayland-ready’. It’s a slow process!

So, you might not know if you’re using Wayland or X11 and this article tells you how to check just that.

Are You Using Wayland Or X11:

This article requires an open terminal, like many other articles on this site. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

With your terminal open, just run the following command: (It should work in any distro, regardless of which display server you’re running.)

echo $XDG_SESSION_TYPE

1	echo $XDG_SESSION_TYPE

The output should look a lot like this:

kgiii@kgiii-desktop~$ echo $XDG_SESSION_TYPE
x11

1 2	kgiii@kgiii-desktop~$ echo $XDG_SESSION_TYPE x11

Unless you’re using Wayland. In that case, it’d look something like this:

kgiii@kgiii-desktop~$ echo $XDG_SESSION_TYPE
Wayland

1 2	kgiii@kgiii-desktop~$ echo $XDG_SESSION_TYPE Wayland

If the output says x11, you’re not using Wayland. If it says Wayland, you’re using Wayland. I probably didn’t need to specify this, but I did. This way, you can be completely sure if you’re using Wayland or x11.

Closure:

See? There’s a fun command you can play around with. If you’re not sure if you’re using Wayland or X11, this command will get you sorted quickly and easily. There are all sorts of great things you can do with an open terminal and a little bit of knowledge.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Let’s Make An Animated GIF (With ImageMagick)

Today’s article is just for fun, where we learn how to make an animated gif in the terminal – with ImageMagick. It’s just for fun and not something you’ll likely need unless you’re some sort of content creator. (We don’t know any of those, do we?) Anyhow, let’s go ahead and make an animated .gif in the terminal.

Today, we’ll be using ‘ImageMagick’. As far as I know, imagemagick has one of the longest and most complicated man pages. It’s huge and a capable tool in the right hands. ImageMagick has all sorts of capabilities but a new user isn’t likely to use them because of the complexity involved.

And, ImageMagick is complex… In fact, it defines itself as:

ImageMagick – is a free software suite for the creation, modification and display of bitmap images.

That’s an accurate description, I think… Except, well, it does a whole lot more than that. We’ll be using the .gif format, while the man page description only mentions bitmap. So, there’s a lot to the application.

Thus, without further ado, we make an animated gif in the terminal…

How To Make An Animated GIF:

The ImageMagick application is terminal-based. So, you’re going to need an open terminal. If you want, you can just press CTRL + ALT + T and your default terminal should open.

If you don’t have ImageMagick installed, you’ll need to install it. If you’re using a mainstream distro, it’s possibly installed already. Otherwise, it’ll certainly be in your default repositories as it’s a pretty major tool. For example, an apt user would just use a command like this (adjust for your package manager):

sudo apt install imagemagick

1	sudo apt install imagemagick

With your terminal now open and imagemagick properly installed, let’s just see how long that man page is:

man imagemagick

1	man imagemagick

See? I wasn’t kidding!

Now, here’s what you need to make an animated gif:

A dedicated folder, perhaps in your ~/Pictures directory.
A few images of the same format, we’ll use .jpg in our example.
A terminal opened in the above-mentioned dedicated folder.

The first thing to learn is that this command is going to take those images and turn them into an animated file with the .gif extension. It is going to organize them alphanumerically. So, you should rename the .jpg files in the order you wish to see them (assuming the order matters to you).

All set? Have you done all those things? Are you 100% prepared? Good!

The command we’re looking for would be:

convert -delay 100 -loop 0 *.jpg <file_name>.gif

1	convert -delay 100 -loop 0 *.jpg <file_name>.gif

Alright, so the ‘delay 100’ is how long each image will be shown – in hundredths of a second. The ‘-loop 0’ tells it to loop infinitely, or you can pick your own number of times. The ‘*.jpg’ means use all the .jpg files in that directory. The ‘file_name’ is the name of the file you want to have as your output.

See? Pretty simple. An example command might be something like:

convert -delay 25 -loop 10 *.jpeg my_animation.gif

1	convert -delay 25 -loop 10 *.jpeg my_animation.gif

Let the command run, and it is a pretty speedy process unless you have a whole lot of images, and you’ll get an animated gif as a result. As these tend to have smaller file sizes, it’s sometimes a better option than sharing a larger video file. It depends on your circumstances, I suppose.

NOTE: This article has been edited to correct the time delay, the delay between changing images. Thanks @wizardfromoz!

Closure:

There you have it. You have an article that tells you how to make an animated gif with ImageMagick. The ImageMagick application has a ton of options, making it daunting for a new Linux user. So, this is just a tiny bite. This is just one of many ways to use ImageMagick. Instead of learning the whole application at once, you can do so in chunks – learning only what you need.

Let’s Have A Happy New Year In The Terminal

Today’s article is going to be just another fun article, where we have a happy New Year in the terminal. Why in the terminal? Because, why not in the terminal? If you want to celebrate the New Year holiday in the terminal, read on and see how.

You won’t learn much in this article, but it can tie back to a couple of previous articles. This is just a fun article. As for articles it might tie into, check these previous articles:

Add A Message Of the Day (MOTD) To SSH
How To: Show An SSH Banner

If you read those two articles, or somehow remember them, you’ll see a common theme mentioned – that is ‘ASCII’. ASCII stands for “American Standard Code for Information Interchange”. Or, in plain language, text.

Text, terminal, and a New Year celebration? Darned right, we’re gonna have fun. Well, maybe not too much fun… But, I promise it won’t be too educational.

Yes, I realize that there are a variety of calendars on the planet. Yes, I know that there are other New Year celebrations. If this isn’t your New Year holiday, though this will technically be posted on my New Year’s Eve day, you can save this article and celebrate it when your holiday rolls around.

So, with all that in mind, let’s go ahead and get into the article…

Happy New Year In The Terminal:

You guessed it, you need an open terminal! So, open one up. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

With your terminal now open, install ‘figlet’.

APT using distros:

sudo apt install figlet

1	sudo apt install figlet

YUM using distros:

sudo yum install figlet

1	sudo yum install figlet

DNF using distros:

sudo dnf install figlet

1	sudo dnf install figlet

You may find ‘figlet’ available for other distros. If you do, you should install it before going on. You will need ‘figlet’ for the remainder of this article.

With ‘figlet’ now installed, you can check the man page:

man figlet

1	man figlet

We’ll just be using a couple of features available with ‘figlet’, but the man page is pretty informative. You can do quite a bit with ‘figlet’.

Using figlet:

While still in your terminal, you can just use ‘figlet’ in its most basic form:

figlet Happy New Year

1	figlet Happy New Year

The output of that command should look similar to this image:

figlet displaying a banner in the terminal — See? You have your terminal saying Happy New Year! Festive, huh?!?

You can also use ‘figlet’ by loading the data from the file. It’s easy enough to use ‘figlet’ to display information from a file, I’ll show you. Let’s use one of my favorites, nano:

Let’s start by making the file:

nano hny

nano hny

Add the following text:

Happy New Year

1	Happy New Year

Now save the file with nano. That’s pretty easy, but I’ll show you. Just press CTRL + X, then Y, and then ENTER. That should save the file as ‘hny’ in whatever directory you were working in.

So, let’s use ‘figlet’ to show the contents of our ‘hny’ file:

figlet -p < hny

1	figlet -p < hny

There you have it. If you go back to the article’s introduction, you’ll see a couple of links. In those instances, you can actually call ‘figlet’ to show the contents of a file, for things like an SSH banner. They all kinda tie together, if you want them to.

Closure:

And there you have it. You have another article. This time, you’ve learned nothing – except how to have a happy New Year in the terminal. Well, you’ve also learned a bit about ‘figlet’, which is nice. Either way, enjoy the holiday and thanks for sticking with me throughout the past year!

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Quickly Restart The Cinnamon Desktop Environment

Today’s article is going to be a pretty quick and easy article, where you learn how to quickly restart the Cinnamon desktop environment. It shouldn’t be a very long article, and I’d say it’s easy enough for a beginner to process. So, if you’re interested in restarting the Cinnamon DE, read on!

Obviously, this will only apply to those folks who are using the Cinnamon desktop environment. Well, no… I do believe it also works in the GNOME desktop environment. As I understand that it’s a holdover from GNOME, which is what Cinnamon is based on. Alas, I don’t have anything running GNOME right here in front of me, so I’m not going to test that.

On the off-chance that you don’t know what desktop environment you’re using, that’s easy enough to learn. You can just read this article:

How To: Determine Your Desktop Environment

If you want to skip reading that, just open the terminal and run the following command:

echo $DESKTOP_SESSION

1	echo $DESKTOP_SESSION

The output of that command will tell you what desktop environment you’re using. If the result is ‘cinnamon’, then this article applies to you!

Anyhow, if you leave your computer on for a long time, you might find that Cinnamon is eating up a bunch of RAM and CPU. You can clear that out by logging out or rebooting, but there’s a much easier way to restart the Cinnamon desktop environment. This article will show you how.

Restart The Cinnamon Desktop Environment:

This time around, you don’t even need to open a terminal!

With your keyboard, press ALT + F2 and you should have a new window open up on your screen. It looks like this:

Now, all you need to do to restart the Cinnamon desktop environment is press the letter R and then press the ENTER key.

That alone, that little shortcut, will restart your Cinnamon desktop environment, meaning it may free up some RAM and lower the amount of CPU that the desktop environment is using.

Bonus:

You can actually run other commands from there. I don’t know all of them, or at least I don’t know if I know all of them. I’ve been unable to find an exhaustive list and I only know of a few shortcuts you can use in this run screen.

There’s a shortcut, like ‘rt’ that will reload your theme (useful for theme creators). It just reloads the theme, and doesn’t actually restart Cinnamon, though it may kinda look similar.

This won’t apply to too many of my users, as my readers are generally beginners, but you can also enter ‘lg’ into the shortcut window.

If you were using GNOME instead of Cinnamon, it’ll open up “looking glass”, the GNOME debugger.

If you’re using Cinnamon, it opens up Melange – the Cinnamon debugger. Debuggers can be useful if you need it and know what you’re doing with it.

The goodness doesn’t stop there!

If you want, you can put ‘firefox’, ‘gedit’, ‘leafpad’ or other applications in there. So long as those applications exist in /usr/bin, they should load just fine from this run screen. You can use this shortcut to open pretty much any application that has been installed via the normal means.

If you want to load something that’s not installed from this screen, you can do that too. You just need to enter the path to the application you want to open. Something like, ~/Downloads/LibreWolf.AppImage will work, according to my testing.

Closure:

There you have it! You’ve learned how to use a hidden run menu to restart the Cinnamon desktop environment. On top of that, you’ve learned that it can be useful for all sorts of other tasks. It’s a pretty handy shortcut, one you can open without taking your hands off the keyboard to use a mouse. That right there is quite a bonus in and of itself!

A Couple Of Ways To Get Your Graphics Card Information

Today’s article is just a simple affair, one where I show you a couple of ways to get your graphics card information in the terminal. If that’s the sort of information you’re looking for, this is the article for you. So, do read on!

Using the commands in this article will give you some details that you probably haven’t committed to memory, so it’s a good way to learn your graphics card information. We’re just going to cover a couple of ways – as this is one of those things that can be learned with all sorts of tools.

This article shouldn’t be all that difficult or very long. It’s suitable even for a beginner, allowing new users to get to a point where they’re more comfortable working in the terminal. You largely just need to cut and paste.

We won’t really be doing anything all that new. We’ll use a couple of pretty standard commands to show hardware information, but we’ll then narrow that information down to just showing the graphics card information. So, this isn’t rocket science, it’s just using the terminal to glean the information we are after.

So, with all that in mind – and no further need to write an intro, let’s just head right into the article…

Find Your Graphics Card Information:

Yup. You guessed it. We’re gonna need an open terminal for this one. So open up your favorite terminal. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

The first command is just using ‘lspci’. The ‘lspci’ command lists PCI (peripheral component interconnect) information. We’ll then use a pipe and grep to extract just the information we’re after and nothing more. The command we’ll use to find your graphics card information would be:

lspci -k | grep -EA3 'VGA|3D|Display'

1	lspci -k \| grep -EA3 'VGA\|3D\|Display'

The second command is nice and easy. We’ll be using ‘lshw’, a command that simply ‘lists hardware’. It’s a handy command and we should do an entire article on it – and likely will. But, it’s really simple:

sudo lshw -c video

1	sudo lshw -c video

Yeah, the ‘lshw’ command requires sudo to gather all the relevant information. There are other tools that don’t require sudo, but this one does. We use it because it’s a pretty standard tool in all the major Linux distros. It’s one of those universal things.

Closure:

There you have it. You have a couple of ways to show the graphics card information in the terminal…

And, son of a biscuit eater… I just noticed I already have an article on this subject. It’s a wee bit different, so I’m just gonna run with this one. Screw it… After this many articles, there’s bound to be some overlap.

Oh well… Oops and all that. I don’t really have time/motivation to delete this one and write a new one.