Language Selection

English French German Italian Portuguese Spanish

Tools for GNU/Linux: Third party screenshot utilities

Filed under
GNU
Linux

I take screenshots more than I do real photos, and I’m a reporter for my college newspaper, as well as have my portfolio etc. That said, I’ve had my share of ups and downs with different software, and have come to find two programs that adore, when using a GNU/Linux system; Shutter and Gyazo.

Both of these programs take screenshots, and do various things with them, but they are drastically different and therefore serve quite different purpose in why I use them.

Shutter, I tend to use when writing articles, or any work that requires me to need the screenshot on my local drive, perhaps to be emailed off or uploaded somewhere. Gyazo, I use when I need to quickly send a screenshot of a funny thing that happened in a game, or of something I found on a website, or anything where it’s just “Hey take a look at this!”

Read more

More in Tux Machines

today's howtos

Android Leftovers

The Spectre/Meltdown Performance Impact On Linux 4.20, Decimating Benchmarks With New STIBP Overhead

As outlined yesterday, significant slowdowns with the Linux 4.20 kernel turned out to be due to the addition of the kernel-side bits for STIBP (Single Thread Indirect Branch Predictors) for cross-HyperThread Spectre Variant Two mitigation. This has incurred significant performance penalties with the STIBP support in its current state with Linux 4.20 Git and is enabled by default at least for Intel systems with up-to-date microcode. Here are some follow-up benchmarks looking at the performance hit with the Linux 4.20 development kernel as well as the overall Spectre and Meltdown mitigation impact on this latest version of the Linux kernel. Some users have said AMD also needs STIBP, but at least with Linux 4.20 Git and the AMD systems I have tested with their up-to-date BIOS/microcode, that hasn't appeared to be the case. Most of the AMD STIBP references date back to January when Spectre/Meltdown first came to light. We'll see in the week ahead if there is any comment from AMD but at this time seems to be affecting up-to-date Intel systems with the Linux 4.20 kernel. Read more

Today in Techrights