While being lately into KDE, I always acknowledged that any non-GNOME-based desktop environment is perfectly usable. Two “no-go” elements: it shouldn’t use Files, the dumbified version of Nautilus that makes it the only file manager in the Universe that lacks a compact list view; and it shouldn’t be designed for tablets. Now, if you consider GNOME as not being designed for tablets or more generally for touch screens, there’s one more possibility: it’s been designed for retards. Either way, some desktop environments are going the wrong way; I agree with comments #2, #4, and #7 from DWW 1087 of Sept. 9, 2024 regarding the new COSMIC desktop: “Any DE that tries to turn my desktop interface into a mobile phone interface will be immediately rejected.” “Of all DEs to go and copy, Gnome. This was an opportunity to really shine and innovate. I guess twin 4K displays can act like a giant tablet, right? I am really, really disappointed.” “I will never use any desktop based on the current Gnome desktop.”

OK, so we’re left with XFCE, MATE, and Cinnamon. Incidentally, the only desktops supported by Linux Mint. But we’ll get to this later.

Why Dolphin?

Why should anyone want to use Dolphin under a GTK-based environment that has a perfect valid file manager?

As I explained on several occasions, I was never a die-hard KDE aficionado. But after I decided to quit XFCE for KDE, a few advantages of Dolphin became apparent, and I want to summarize two features unique to Dolphin.

❶ Qt and KDE fix a bug in the Linux Kernel regarding exFAT and FAT32. As explained in Why KDE, part IV: Qt and KDE fix a bug in the Linux Kernel, Linux has a kernel bug that only Qt works around.

The man page for mount.exfat-fuse(8) wrongly considers that “exFAT is a case-insensitive file system.” A more accurate definition would be case-retentive: it knows the difference between names that differ in case, but won’t let you create two files with names that differ only in case.

So you can’t have both A File Name.txt and A file name.txt in the same directory on exFAT and FAT32. This is by design: the idea is to allow mixed-case file names, without the cost of actually allowing several files that would be identical if case were neglected. That’s because internally, exFAT and FAT32 are indeed case-insensitive: they need to compare file names converted to upper-case during search and other file operations. This is why such file systems cannot accommodate two files that would convert to the same all-caps name!

You’ll get issues when trying to rename A File Name.txt into A file name.txt or vice versa. Not under Windows, although even there you might need to hit F5 to refresh the view and see the new file name correctly. But under Linux: mv would fail, and so would Caja, Files (Nautilus), Nemo, Thunar, PCManFM and PCManFM-Qt (which still uses GTK-based file operations)! I posted 6 screenshots to prove it. Dolphin is the only file manager to work around this limitation and to behave like File Explorer (Windows Explorer)!

Since the Linux kernel team couldn’t care less about false error messages during renaming operations, Qt’s and KDE’s developers took the situation in their own hands: I listed the relevant changes in FileProtocol::rename and QFile::rename. Their approach avoids error messages under both FAT32 and exFAT. Their own comments:

// rename() on Linux simply does nothing when renaming "foo" to "Foo" on a case-insensitive
// FS, such as FAT32. Move the file away and rename in 2 steps to work around.
...
// rename to temporary name
...
// rename to final name

💡 So, should you be using exFAT or FAT32 devices, such as flash drives or external SSDs or HDDs, you might need to use Dolphin to fix the case of files or folders: any other file manager would refuse to rename such files or folders, claiming that they exist!

❷ Here’s another thing where Dolphin is the only major file manager that works as expected, and all the others just suck: when canceling a file copy operation!

What do you expect when you’re using a graphical file manager to copy a large file to a slow destination, and you change your mind, so you hit the Cancel button? The file manager should cancel the copy operation graciously, by issuing a fclose() followed by remove(), so that nothing remains in the destination. This is what Windows has been doing since, like, forever. Not so in the open-source land. Here, only Dolphin does that! All of the following file managers leave incomplete, broken files in the destination: Files (Nautilus), Nemo, Caja, Thunar, PCManFM, PCManFM-Qt. The problem with such broken, incomplete files is that people would assume they’re complete, valid files! “Oh, so those files got copied, great.” Except that they weren’t!

More details in A few words on KDE.

💡 I sincerely don’t know how can one be a developer of any of the aforementioned file managers (SIX OF THEM, practically everything that is not Dolphin and that has a relevant user base!) and not caring about this HUGE BUG! I can’t believe that nobody canceled a slow copy, and they didn’t notice the remaining broken files! Are open-source developers, as a rule, mentally retarded?

Here’s a use case: As a backup, I want to copy a bunch of files to an external device that isn’t a SSD, therefore it’s slow. Say they’re movies, hence large. At some point, I decide to split the copy on two devices, because there’s still some space on another, faster device. I click Cancel or hit ESC and, after the copying has stopped, I look at the copied files, so that I should copy to the other device only the remaining files. But the last copied file is not complete, and I can only notice that by comparing the file sizes!

Unacceptable. Use Dolphin if such a scenario has a chance of happening to you.

Let’s start with… Ubuntu MATE

The easiest way should have been Linux Mint, because it has all three GTK DEs that are not GNOME3/4x, with the extra addition of uniform theming and some common XApps such as Xed instead of Pluma and Mousepad (this might annoy some people, but it’s part of their uniform feeling, I guess). When I wrote Linux Mint: by no means, that was in the context of KDE, but among the negative parts, beyond it taking too long to switch from an Ubuntu LTS release to the next one (KDE neon is even slower to switch!), I forgot the most important disadvantage to me: it’s theming is so bland and ugly, that it would push me to clinical depression and potentially suicide if I used it! The icon theme is also horrendous (is this a smartphone?), with a really dumb Firefox icon.

OK, the theming can be changed, but the main advantage of a strongly-themed distro (Manjaro, anyone?) is to make it completely usable out-of-the-box, bar some change of wallpaper and of a color theme from the provided ones. Remember that no other DE is as easily and as radically customizable as KDE. This being said, the default XFCE theming and layout sucks big time (the ugliest XFCE distro being Xubuntu), and the unthemed MATE also looks too much like it’s 2010, both having pathetic out-of-the-box customization options (I’m not talking of xfce4-panel-profiles or of mate-tweak, but of themes and icons). Fortunately, Mint comes with custom themes; unfortunately, they suck big time.

So I thought it smart to start the distro in which MATE looks at its best: Ubuntu MATE.

Qt/KDE apps and Dolphin in Ubuntu MATE

There are many ways of trying to ensure that GTK-based and Qt-based programs are themed more or less identically. The way you’re doing it depends on whether you run a GTK-based DE (XFCE, MATE, GNOME, Cinnamon, LXDE) and wish to theme Qt, or you run KDE (or LXQt) and want to theme GTK2/3 apps. I became more used to how to get a matching GTK theme under KDE than vice versa. Either way, this article from Arch’s wiki is a good starting point: Uniform look for Qt and GTK applications.

The default Ubuntu MATE theme is Yaru-MATE-light. The direct opposite alternative is Yaru-MATE-dark. All the other themes are variations of these two, in the sense that they’re either completely light or completely dark. There is no “twilight” theme like Ubuntu once had, meaning there’s no way to have a generally light theme, but with dark panels, start menu, and title bars. (There is a way: use Linux Mint MATE: the start menu will be light gray, but the panel and the title bars almost black.) The main disadvantage of any light theme in Ubuntu MATE is that MATE Terminal will default to a white background, which you’ll want to change.

💡 IMPORTANT NOTE! I installed both Dolphin and PCManFM-Qt because every single Qt/KDE5 app will behave like PCManFM-Qt, except for Dolphin, which is a special case. Note that for Dolphin to display the Icons, Compact, and Details toolbar icons instead of text, breeze-icon-theme must also be installed.

❶ With the default theme or any light theme, everything is just fine:

The only annoying thing is that bottom-right area where Dolphin displays “… GiB free” and whose default 3D look is completely outdated.

❷ With any dark theme, Dolphin is running amok:

Once the shock gone, a legitimate question arises: why Dolphin and Dolphin alone?

Also, the alternating colors in the Details mode is just jaw-dropping!

First, let’s say that Ubuntu MATE does not use any of the following ways of theming Qt: adwaita-qt, qt5ct (and qt5-style-plugins), Kvantum, QGnomePlatform. Instead, what it does is to use GTK2-based theming (libqt5gtk2 and qt5-gtk2-platformtheme), despite the host DE being GTK3-based. But Qt/KDE can use GTK2 themes, that’s why.

In Ubuntu MATE, you’ll find in /etc/profile.d/mate-qt.sh:

# MATE Desktop Qt integrations
if [ "x$DESKTOP_SESSION" = "xmate" ] || [ "x$XDG_SESSION_DESKTOP" = "xmate" ]; then
    # QT apps to use GTK styling
    export QT_QPA_PLATFORMTHEME=gtk2
fi

Also,

$ echo $QT_QPA_PLATFORMTHEME
gtk2

So let’s try the old way. After sudo apt install qt5ct qt5-style-plugins and making sure that echo $QT_QPA_PLATFORMTHEME spits out qt5ct, I noticed that the qt5ct theme was completely ignored by all Qt apps. Eek.

One possible approach would then be to look into each dark theme, say /usr/share/themes/Yaru-bark-dark/gtk-2.0, and try to fix things in one or more of the files gtkrc, main.rc, apps.rc, hacks.rc.

Strange thing, in /usr/share/themes/Yaru-bark-dark/gtk-2.0/main.rc you’ll find the alternate row colors, but Dolphin doesn’t seem to care:

  GtkTreeView::odd-row-color        = @base_color
  GtkTreeView::even-row-color       = @base_color

The way Dolphin interprets the GTK2 theming is… nonchalant. BTW, here’s Dolphin not respecting the GTK theme in Sway.

What next?

I’ll cover (with screenshots) Linux Lite a bit later, but let’s try to get inspiration from its XFCE configuration. In Linux Lite:

$ echo $QT_QPA_PLATFORMTHEME
qt5ct

Just as I would do in Linux Lite, setting in qt5ct the theme to gtk2 has the same effect that every single Qt/KDE app will use it, but Dolphin.

Actually, qt5ct is only useful if you want to also use for Qt5 other styles than GTK2.

Arch to the rescue: Mismatched folder view background colors. Here:

When running Dolphin under something other than Plasma, it is possible the background color in the folder view pane will not match the system Qt theme. This is because Dolphin reads the folder view’s background color from the [Colors:View] section in ~/.config/kdeglobals. Change the following line to the RGB value you prefer (it may be given in the form #RRGGBB or R,G,B):

~/.config/kdeglobals

...
[Colors:View]
BackgroundNormal=#2E2E2E
...

OK, this would fix the problem with dark themes:

But look what happens with light themes:

Another idea, this time from StackExchange:

I somehow fixed it by adding a new stylesheet in qt5ct, with the content below:

QMenuBar {
}

This above code pretty much does nothing. And I’m pretty sure any selector would work. But I am not sure why adding a simple blank CSS definition would fix the problem.

Nope. That worked 5 years ago, but not anymore.

Also, have you noticed the dotted frame around the last selected folder or file? It’s impossible to get rid of it, one item has to have this frame!

Someone asked on Reddit 2 years ago, to no avail. No fix.

I tried all the possible hacks in the known Universe, I just can’t make it disappear! For instance, I tried .qss files in which I played with such things:

QItemView::item:selected:focus {
 outline: none;
 border: none;
}
QItemView::item:focus {
 outline: none;
 border: none;
}
QItemView::item:selected:not(focus) {
 outline: none;
 border: none;
}
QItemView::item:selected {
 outline: none;
 border: none;
}
QFocusFrame {
 outline: none;
 border: none;
}

Wishful thinking. The real problem is how Dolphin, and Dolphin alone, is theming itself under GTK.

Remember Ubuntu’s Ambiance theme?

That one that was replaced with Yaru since Ubuntu 20.04. It has not been discontinued, and it can be installed with sudo apt install light-themes (from Universe), which also installs Radiance. However, it’s not suitable for MATE, as it will not theme the panel and the start menu, but only the Indicator Applet and the title bars.

Note that I am using the “Redmond” layout:

The Humanity icon theme is horrendous, so you might prefer the Yaru icons:

Nope. We need something better.

Enter Luke Horwell’s PPA for Ambiant-MATE Themes:

Ubuntu MATE’s fork of the Ambiance and Radiance GTK theme.

This theme was used for Ubuntu MATE since it’s debut in 14.10 until 20.10.
It is now community supported.

Supports 22.04 and later.

https://github.com/lah7/Ambiant-MATE
https://github.com/lah7/Ambiant-MATE-Colours

To get Ambiant-MATE, Ambiant-MATE-Dark, and Radiant-MATE:

sudo add-apt-repository ppa:lah7/ambiant-mate
sudo apt install ambiant-mate-gtk-themes ambiant-mate-icon-themes

It’s also possible to install 9 color variations: ambiant-mate-colours-aqua, ambiant-mate-colours-blue, ambiant-mate-colours-brown, ambiant-mate-colours-orange, ambiant-mate-colours-pink, ambiant-mate-colours-purple, ambiant-mate-colours-red, ambiant-mate-colours-teal, ambiant-mate-colours-yellow; or get them all (sudo apt install ambiant-mate-colours-all), but the 35 MB download would unpack to 550 MB!

Now, Ambiant-MATE works fine, and it provides a “twilight” theme that leaves the contents of the windows light, but darkens the title bars, the panels and the start menu (and the terminal):

Note that the Arch-inspired kdeglobals hack (the BackgroundNormal color) has been disabled.

The problem arises, as expected, with Ambiant-MATE-Dark:

Dolphin is not made for dark GTK themes! If you’re 100% sure you won’t use it with light themes, that hack suggested by Arch can be considered an acceptable workaround. Otherwise, the contrary applies: just don’t use dark themes!

But there’s one more thing. When using Mate Tweak to switch to the Redmond layout, it defaults to having the Disk Mounter applet added to the panel. And those icons really look like shit to me:

No problemo, just customize the theme to switch back to Yaru-MATE-light icons:

Interlude: Is the dark mode really what you need?

We have all started from terminals with a black background, regardless of the text color (green, white, light gray, or off-white). But documents with lots of text usually had a white background, even in the times of CRTs, when that was more than harmful to your eyes. I’m not sure what made the dark themes so popular, but I agree that there were many factors, such as:

  • The general theory is that dark themes can reduce eye strain, especially in low-light environments.
  • Many people started using Samsung smartphones, and on OLED and AMOLED screens, dark themes can conserve battery life.
  • The minimalist, hipsterish design trend of the 21st century made dark themes trendy.
  • People started to use dark modes in their code editors and IDEs, not just in terminals.
  • The gamers also preferred dark modes.
  • Finally, Windows 10 added a dark theme, and all the sheeple followed. Dark modes are preferred by most Arch users, but also by many users of other distros.

What I can say, based on my own experiences:

  • Dark modes are great in terminals and generally on smartphones.
  • They are less practical when you have to read long texts, such as documents or e-books. On my smartphone, I use a grayish-yellowish background (not that dumb sepia!) to read ePubs, because otherwise I just cannot read them! Reading a book is associated to a light background, not with a VT100 terminal! This is a good reason to use an e-Ink reader, but I prefer my smartphone, with a low brightness and a light background that is not white.
Black background? Over my dead body!

There is an explanation for that. All About Vision® (masthead, ours en français), an EssilorLuxottica partner: Is dark mode better or worse for your eyes?

While dark mode has a lot of benefits, it may not be better for your eyes. Using dark mode is helpful in that it’s easier on the eyes than a stark, bright white screen. However, using a dark screen requires your pupils to dilate which can make it harder to focus on the screen.

Why does eye dilation make it harder to see? When your pupils dilate, your vision becomes less clear. When your pupils constrict under bright light, your vision sharpens. Just like a camera, a smaller aperture provides greater depth of focus. For this reason, it may be more difficult for some people to clearly see screen details in dark mode.

People who have myopia or astigmatism also may experience halation (from the word “halo”). Halation occurs when light spreads past a certain boundary, creating a foggy or blurry appearance.

In other words, white letters can appear to bleed into a black background, making it more difficult to read, especially if the print is fine.

Halation is more common and more severe when using dark mode, so those who already have vision issues may benefit more from a dimmed light mode or blue-light-filtering mode.

Traditional wisdom said that you shouldn’t watch TV in a completely dark room, unless you add a lightbulb behind the TV, so the eye won’t perceive a stark contrast between the screen’s light and its surroundings. This has nothing to do with the CRTs; it’s a rule still valid today, but people are increasingly stupid. They are also screwing their eyes and nerves by keeping the LCD (which hopefully is IPS and not TFT) at maximum brightness while inside. What people need is being less stupid, not a dark mode!

I admit, however, that it kind of makes sense that for many people, coding feels better on a darker screen, albeit not necessarily black. 💡 Here’s a collection of 800 themes for VSCode: most of them are dark and appealing (except for a few that include pure blue on black!), but a few light ones seem nice, too! In the end, the programming code is neither fiction nor textbooks, and its colored syntax makes it readable in many color schemes.

I tend to prefer something retrogroove, but not too pale. 💡 Here’s the original gruvbox theme for vim, and its ports to other text editor and apps: e.g. for Sublime Text here and here, and for VS Code here and here.

Linux Lite is next in line

Linux Lite is, arguably, the best-looking XFCE distro there is. Sharing the same disadvantage with Mint, Lite is only following LTS releases, and even so, it’s not very fast to rebase to the latest LTS (faster than Mint, usually).

Three and half years ago, in A Community Experiment in Two Linux Distros, I shared my experiences with a failed communication with both Ubuntu MATE’s and Linux Lite’s communities and developers, mostly based on divergent values. The MATE guys refused to admit that forcing the Yaru-MATE themes as snaps is absurd, if not even abject, and the Lite’s sole developer failed to acknowledge that the bugs I reported were indeed bugs. And yet, these two distros are worth considering. When people were relatively happy with Win95, Win98, or WinXP (I was happy with Win3.1 too!), did they have to love Microsoft?

I just tried Linux Lite 7.2-rc1 to see if it behaves differently than 7.0. It doesn’t. It has the exact same bugs. For instance, the live session has Chrome installed, but it doesn’t work because the live user is poorly configured, and nobody bothered to fix this bug:

The installed system, fixes this, but the battery applet (Power Manager Plugin) isn’t added by default to the panel, and the Package Updated Indicator is too bright and too orange even when there are no updates. Finally, what has always bothered me at Linux Lite is that regardless of the theme used, it’s very difficult to grab the bottom-right corner to resize it on two directions. It must be a window manager setting, but I could never be bothered to hack anything in XFCE. The workaround is to use Alt+Right-click-and-Drag to resize a window. Lite also has the Alt-F8 shortcut, but this too can be changed.

But let’s try to use Qt-based software.

$ echo $QT_QPA_PLATFORMTHEME
qt5ct

Cool. The classic way. However, by default, all Qt windows will look the same in both light and dark themes, because they don’t follow the GTK theme, and the only available styles are Fusion and Windows, so Qt5ct is useless. But at least, nothing is broken!

sudo apt install qt5-style-plugins

Now “gtk2” can be selected in Qt5ct:

But you know the drill:

The same hacks tried in MATE will have the same effects in XFCE. It’s up to anyone to decide what they want to do.

Oh, wait, Qt5ct could also use Kvantum. Let’s try it again after this:

sudo apt install qt5-style-kvantum qt5-style-kvantum-themes

Strange enough, the themes “kvantum” and “kvantum-dark” look just the same, meaning they’re dark:

This is a terribly ugly Qt5 theme, not matching in any way the flatter GTK themes, but at least it’s a dark theme that can be used to theme the Qt/KDE software! The method would also work in MATE.

What’s more shocking is that a bug present in Linux Lite 7.0 is still with us in 7.2-rc1. It looks like nobody is using a dark theme in Linux Lite!

Any dark theme from those installed will break the background color for the line numbers gutter in GTK-based text editors!

It breaks Mousepad, which is the default text editor in XFCE and which has the line numbers enabled by default! Hello, Jerry Bezencon, what in the fucking hell are you testing there? It also breaks Pluma, MATE’s text editor, in which line numbers have to be manually enabled.

This bug is specific to Linux Lite, but apparently also to an obscure distro called Lilidog Linux. There, the forum provided a fix in May, 2023 (they claim to have noticed this bug “in other distros, both Arch- and Debian-based”): edit ~/.config/gtk-3.0/gtk.css and add this rule:

textview border {
	background-color: #363B42;
}

It works! (That color can be changed to anything else that’s a darkish color.)

GTK themes are controlled by GNOME, which means Red Hat is the entity responsible for breaking them. But Jerry Bezencon did absolutely nothing to fix this older bug.

Linux Mint Cinnamon, MATE, XFCE

Linux Mint, the distro cherished by so many people! I’ll never understand why. As I said, I’d feel suicidal if I were forced to use the original theming, no matter the color accents they’re so proud of! Some say that using Ubuntu, any flavor of it, makes you mediocre. (It’s an euphemistic way to say that only idiots use Ubuntu, possibly because “Linux==Ubuntu” for some.) If so, I’d add that only the “complete mediocre” use Linux Mint!

I’ll never install Linux Mint again. I have used it when they introduced the XFCE edition, I guess. Possibly with MATE, too. More than a decade ago. Not going to do it again. But they have Live ISOs for each edition, right?

Once you change the default theme to the exact same theme in its dark variant, you’ll notice that there’s no attempt to theme the Qt-based apps.

Linux Mint Cinnamon edition:

Linux Mint MATE edition:

Linux Mint XFCE edition:

En passant, I’d like to point out to the fact that changing the theme alone doesn’t darken the window decorations in XFCE! The title bars are still light gray even for GTK! While XFCE lags behind all the other desktop environments regarding theming, and the themes that come with it are absolutely terrible (take a look at Xubuntu), there are distros that offer better themes. It’s actually more sensible to have a “mixed” (or “twilight” in KDE lingo) theme with light window contents and dark title bars and panels than the other way around. Manjaro XFCE is a good example.

Back to Qt/KDE lack of theming, there is an explanation for that: echo $QT_QPA_PLATFORMTHEME doesn’t print anything, as nobody sets this variable.

Ubuntu MATE sets QT_QPA_PLATFORMTHEME to gtk in a profile script, which helps, unless you want to use Dolphin with a dark theme. Linux Lite sets QT_QPA_PLATFORMTHEME to qt5ct, because it has Qt5ct installed. Qt5ct allows you to choose between a couple of Qt themes, gtk, or a few extra Qt themes, should you install them (see Kvantum). So the most flexible solution would be to install Qt5ct, right?

Wrong. Qt5ct SEGFAULTS in Linux Mint Cinnamon:

Then, Qt5ct SEGFAULTS in Linux Mint MATE:

No surprise, Qt5ct SEGFAULTS in Linux Mint XFCE:

Maybe it would work in an installed system, but I’ll never know. Or maybe Mint managed to break Ubuntu. Extra bugs are what everyone pined for!

I’m used to live-only bugs. For lack of proper live user rights, Chrome can’t run in Linux Lite. For another live user misconfiguration, Spectacle in Kubuntu can’t use KDialog for saving files. These bugs don’t happen on an installed system. But to have a segmentation fault, that’s unacceptable! I have tried to find the reason for this SEGFAULT back in July, to no avail.

This Linux Mint experiment ends here. I will continue to despise Mint, and I will refuse to use Cinnamon, the desktop that’s the child of the same team (of Clem’s, actually). Regarding Cinnamon, I’ll quote myself:

Cinnamon is poorly designed, UI/UX-wise. Go here and look at what I described under “Let’s compare XFCE, MATE and Cinnamon in terms of how to define keyboard shortcuts” to see what I mean. Up to, and including “The window below cannot be made smaller, not even in width:”. (OK, you can add several shortcuts for the same action in Cinnamon, but for this to happen, you need more clicks to do anything, and you can’t see everything at a glance. Added complexity that sucks. And wasted lateral space as a general rule. Did I mention that I hate Cinnamon?)

Why did Clem leave MATE to create a derivative called Cinnamon? I hate him.

If you’re really into Cinnamon, there’s absolutely nothing wrong with Ubuntu Cinnamon: it’s an official flavor, it has a better compatibility with 3rd-party software for Ubuntu, it exists even for non-LTS versions of Ubuntu, and it looks much better than Linux Mint! Oh, those snaps? You can make sure that Firefox and Thunderbird are installed from Mozilla’s PPA easier than you thought! (I’l write about this in a later post.) As a consolation prize: Ubuntu Cinnamon 24.04.1; Ubuntu Cinnamon 24.10 Beta; a quick look at it; another quick look.

A false hope, also a fault of Linux Lite’s

I used to be quite a fan of JFS. So I was stunned to notice this option in Linux Lite’s installer:

Wow, so could I really install it on a JFS-formatted partition? It did let me select JFS for a file system!

Nope. It was all a lie!

As a last criticism targeted to Jerry Bezencon. The installer window has a height of 606 pixels. The list of devices and partition has a height of 133 pixels, and it accommodates a header, 3 lines, and just a bit of another line to suggest that there is more. Who was the retard who designed such a shit? It can’t be maximized, and I can only see 3 lines out of the 16 that I had there! The top and bottom black strips are completely useless as a design feature if my blood pressure doubles because I can’t fucking see my devices and partitions but 3 lines at a time!