Fedora 36 Review, a few issues that still need to be fixed
Tags: opensource, beginners, productivity, linux
Published: 2022-06-28 03:21:14

Today, I will talk about the issues that are presenting on Fedora 36 or Linux in general, but they are in the process of being fixed. I will focus on the issues that would likely affect everyone's daily tasks on their computer, hence should be fixed as soon as possible.

Note that, the issues don't need to be directly related to Linux, Fedora, or GNOME. Nevertheless, I have to face these issues as a Fedora 36 user. Therefore, I think it would be worth mentioning in this post. 

> **However, don't hold your breath, take it with a grain of salt as no one knows exactly when these issues will be fixed.**

---

## Hardware acceleration for video decoding on Linux web browsers

![Old man looking at some used retro cams](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/jxw7jksuzcw402z6vohv.jpg)

What is **_hardware acceleration_**? Basically, if a computer task is programmed to use the fastest/specialized processing unit for that task, it's considered to be hardware accelerated.

> **The fastest processing unit for video decoding is Graphics Processing Unit or GPU for short.**

Well, if you watch a lot of videos on YouTube in FHD or 4K, especially on a low-end PC, you would likely need those videos to be hardware accelerated on your web browser.

Sadly, video hardware acceleration on Linux web browsers only **available on Firefox version 101 or above**. You can see in **[this Fedora Wiki page](https://fedoraproject.org/wiki/Firefox_Hardware_acceleration)** for more info on how to set up Firefox for video hardware acceleration.

On Google Chrome or other Chromium-based browsers, you _will not get_ hardware acceleration for video decoding on Linux unless you use a custom-built version of Chromium which only available on some Linux distros, for instance, on **[Raspberry Pi OS](https://www.raspberrypi.com/software/)** that ships a modified version of Chromium through the **[Pi-Apps](https://github.com/Botspot/pi-apps)**.

Currently, the team on Chromium are working hard to get the video hardware acceleration working on Linux, as this is set to level 1 priority on their issues list. See **[Chromium issue #1236697](https://bugs.chromium.org/p/chromium/issues/detail?id=1236697)** for more info.

Therefore, you can expect to see hardware acceleration for video decoding on every Linux browsers soon.

### Caveat: hardware acceleration on DRM protected videos

Sadly, you won't get this on Linux.

There are 3 popular DRM technologies being used to protect online streaming video contents:

- **[Widevine](https://developers.google.com/widevine/drm/overview)**, used in Chrome/Chromium browsers, Chrome OS, Firefox, and Android devices. Basically, this is the standard technology on Google ecosystem.
- **[PlayReady](https://www.microsoft.com/playready/overview/)**, used in MS Edge on Windows 10-11 (sorry, Linux version of MS Edge doesn't support PlayReady), TVs, and TV Boxes. It's a technology from Microsoft.
- **[FairPlay](https://developer.apple.com/streaming/fps/)**, used in Safari and Apple devices. Basically, it's made by Apple for Apple ecosystem.

Linux uses **Widevine** that's shipped in the desktop version of Chrome or Firefox, which is **[Widevine L3](https://en.wikipedia.org/wiki/Widevine#Security_levels:~:text=L3%E2%80%95%20Software%2Dbased%20DRM%20only.)**, which **only supports software decoding**. As a result, DRM protected videos, Netflix videos for instance, will not use hardware acceleration when playing in Chrome or Firefox on any platform/OS, **except for Chrome OS** that has implemented **[Widevine L1](https://en.wikipedia.org/wiki/Widevine#Security_levels:~:text=L1%E2%80%95no%20resolution%20or%20HDR%20restriction%3B%20highest%20level%20of%20protection.%20Both%20cryptography%20and%20media%20processing%20operations%20occur%20in%20a%20trusted%20execution%20environment%20(TEE).)**, which supports hardware decoding, enabling Chrome on Chrome OS to use hardware acceleration when playing DRM videos.

It's worth mentioning that **Widevine is not available for Linux on ARM64 architecture**. Therefore, Raspberry Pi4 users will have to install Chromium 32-bit version even when they are running on 64-bit OS. Otherwise, it would be impossible to play Netflix or other DRM protected videos. See **[Bugzilla #1612995](https://bugzilla.mozilla.org/show_bug.cgi?id=1612995)** for more info.

PlayReady and FairPlay capable devices/OSes can use hardware acceleration when playing DRM videos without any issue.

A complete list of available DRM technologies on all platforms can be seen [here](https://castlabs.com/resources/drm-comparison/).

#### A note to all Netflix members

- Netflix streams 720p videos through Widevine L3 enabled browsers. Basically, for desktop, it's the desktop version of Chrome or Firefox. You can **[manually install Widevine in Chromium](https://github.com/proprietary/chromium-widevine)**, though, but I don't recommend this route.

- **[Netflix streams 1080p](https://help.netflix.com/en/node/296?q=chromebook&ba=SwiftypeResultClick)** videos through Widevine L1 enabled browsers. As far as I know, for desktop browsers, only Chrome on Chrome OS uses Widevine L1.

- You can play Netflix's 1080p videos and also 5.1 sound on Widevine L3 enabled browsers by using **[this Chrome extension](https://chrome.google.com/webstore/detail/netflix-1080p/cankofcoohmbhfpcemhmaaeennfbnmgp?hl=en)** or **[this Firefox extension](https://addons.mozilla.org/en-CA/firefox/addon/netflix-1080p-firefox/)**. However, you will need a more powerful hardware as Widevine L3 doesn't support hardware acceleration like Widevine L1 on Chrome OS. This is also the reason why Netflix 1080p is available by default for Chrome on Chrome OS.

- **[Netflix streams 4k or Ultra HD](https://help.netflix.com/en/node/13444)** videos on MS Edge for Windows (PlayReady), Netflix app for Windows (PlayReady), and Safari on macOS (FairPlay).

---

## Dark Mode on Chrome/Chromium browsers

![Stranger Things](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ysenl4bf0804ls5xosmd.jpg)

Normally, any modern web browser should be able to tell the website whichever Light or Dark theme that the users are using on their system. This feature is called **[CSS prefers-color-scheme](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme)**.

However, Chrome or Chromium-based browsers on Linux are unable to do that due to **[Chromium issue #998903](https://bugs.chromium.org/p/chromium/issues/detail?id=998903#c93)**. For instance, you might set your system to dark theme, but the website will still show its light theme to you. The issue is set to level 2 priority. Therefore, we can expect it to get fixed soon.

---

## Linux and fractional scaling in 2022

![Scale](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/frkyy8et67a88mm53uci.jpg)

Unfortunately, it's not ready yet in 2022. For instance, ~~**Blender** (see **[maniphest T90676](https://developer.blender.org/T90676)**)~~ **[Blender 3.4 introduced Wayland support](https://code.blender.org/2022/10/wayland-support-on-linux/)** and **Godot** (see **[proposal #990](https://github.com/godotengine/godot-proposals/issues/990)** and **[PR #57025](https://github.com/godotengine/godot/pull/57025)**) still have blurry UI with fractional scaling on Linux. **GIMP** has been making a lot of progress in their _development branch_ to **[move from GTK2 to GTK3 since 2.99.2](https://www.gimp.org/news/2020/11/06/gimp-2-99-2-released/)**, thus native Wayland supported. However, I don't think it will be ready before 3.0. You can see the progress at **[GIMP's Wayland issues](https://gitlab.gnome.org/GNOME/gimp/-/issues?page_before=eyJjcmVhdGVkX2F0IjoiMjAyMC0xMS0wOCAxMTo0ODoyMS4wNTU3NDcwMDAgVVRDIiwiaWQiOiI5NjUzOCJ9&sort=created_date&state=opened&label_name[]=Environment:Wayland).** I beleive the list of apps that are still making their way to support Wayland, and thus fractional scaling, would be a lot more than I could ever put it here.

In short, fractional scaling on Linux is not ready for profesional use yet. But I think it's ready for average users (not media creators) and you should enable it.

Well, fractional scaling has been implemented in Linux for a while now as an **_experimental feature_**. That's the reason why it's not enable by default even on Fedora 36! However, you can manually enable fractional scaling feature in Fedora 36 by running this line in the terminal:

```
gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
```

After running this line in the terminal, you will have to re-login to your session again. Then, you should see the fractional scaling in the display settings, as shown in the screenshot below:

![fractional scaling enabled](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/tjzdggj42mxzt8qn60sq.png)

As of today, most of my daily apps won't be blurry with fractional scaling enabled since I mostly use PWAs (Progressive Web Apps) and GNOME apps (because they're beautiful).

Let me show you guys some apps (from my personal experience) that may be blurry at first, but we can fix it right away.

### Chrome / Chromium

Chrome or Chromium-based browsers has a blurry UI when using fractional scaling. However, you can easily fix this by:

1. Enter `chrome://flags` in the address bar, then hit enter.
2. Search for **Ozone** then change the option flag to **Wayland**, as shown in the screenshot below:

     ![Ozone Wayland](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/k7j3v8m3ay0775lrias7.png)

3. Restart the browser, and you are good to go.

And it's not only Chrome that will have a sharp UI, now all of your PWAs (Progressive Web Apps) will all be sharped too. 

There's also another **benefit from enabling** this **Wayland feature in Chrome.** If you are a laptop user, **you can pinch-zoom with your touchpad now.** 

### Telegram

Telegram for Desktop is fast and fluid. However, it's very blurry with fractional scaling enabled. Well, you shouldn't use its desktop app. You can use **[Telegram for Web](https://web.telegram.org/)** instead.

### Various ways to deal with FHD display

1. Use a lower resolution instead. This method won't look good on text (it won't look too bad), but it works very well for UI elements.

2. Install **[GNOME Tweaks](https://gitlab.gnome.org/GNOME/gnome-tweaks)** which can be installed directly on the Software Store. Then, open the app and change the fonts' scaling factor to be above 1, as shown in the screenshot below:

     ![GNOME Tweaks](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zy8vapjtldxg5cy2npan.png)

3. Use the full resolution of your screen/monitor, then use the scaling factor inside the app (if there's any). This works best if you have a multi-monitors setup, i.e. having one monitor for a specific app. For instance, in **Blender**, go to **Edit > Preferences > Interface > Display > Resolution Scale**, and change the scale value as shown in the screenshot below:

     ![Blender's Resolution Scale](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rwem3lnzseffzqh5dlvd.png)

> If you're interested to keeping up with the current state of this feature, you can see it in **[this PR for Wayland](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/143)** and **[this PR for XWayland](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733)**.

---

## Mouse wheel scrolling speed configuation in GNOME

![Car Wheel](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8g1fg27mbdvmpb1ojlcw.jpg)

If that's not obvious enough, let me tell you this: mice has been dominant HID (Human Interface Device) in PC history. But the ability to adjust one of the most used interface (scrolling) for this dominant HID has been missing in GNOME, the most used desktop environment in Linux world, nonetheless. And it's sure enough that **[Windows](https://support.microsoft.com/en-us/windows/change-mouse-settings-e81356a4-0e74-fe38-7d01-9d79fbf8712b)** and **[macOS](https://support.apple.com/guide/mac-help/change-your-mouses-response-speed-mchlp1138/mac)** are providing this setting for their users.

Fortunately, KDE implemented **[this setting for mice and touchpads](https://pointieststick.com/2020/04/11/this-week-in-kde-libinput-scroll-speed-dolphin-remote-access-improvements-and-more/#:~:text=It%E2%80%99s%20now%20possible%20to%20configure%20the%20scrolling%20speed%20for%20mice%20and%20touchpads%20when%20using%20Wayland%20(M%C3%A9ven%20Car%2C%20Plasma%205.19.0))** in Wayland. But I am not a fan of their UI design language. I may try KDE 6 in the future if they improve on this aspect.

In GNOME, there's an **[issue opened to implement this feature](https://gitlab.gnome.org/GNOME/gtk/-/issues/4793)**, along with the **[PR to add this feature in the settings](https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4672)**. I hope this will be fixed soon as the scolling speed in Chrome, Chromium-based browsers, or Electron apps is very slow. There's a Chromium Bug for this, but it's **[closed as WontFix](https://bugs.chromium.org/p/chromium/issues/detail?id=521211)**. Well, at this time, if you're not using KDE, you can use **[this Chrome extension](https://chrome.google.com/webstore/detail/linux-scroll-speed-fix/mlboohjioameadaedfjcpemcaangkkbp)** to fix the scolling speed, both in Chrome and PWAs. But it won't work on all pages though.

> If you're using Linux on X session, there's a CLI tool called **[IMWheel](https://src.fedoraproject.org/rpms/imwheel)** that's used by many for adjusting the mouse wheel scolling speed. However, it's not working in Wayland.

---

## Thumbnails view for the file selection dialog in GNOME

![A Man Looking Photos](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9wwxjklv2j45mznwf41w.jpg)

This GNOME issue is very notorious among Linux users. Well, **[this issue has been opened for 18 years!](https://gitlab.gnome.org/GNOME/gtk/-/issues/233)** Why the thumbnails view for the file selection dialog is a very important feature to have? Let's imagine that you want to pick up one of the 100 pictures in your folder for editing or whatever, what do you want to see, a bunch of file names or a thumbnail previews of those pictures?

Again, this is not an issue in KDE. Therefore, if anyone can't live with this issue, you better go to KDE. I, somehow, live with this issue by drag-and-drop a file that I want from Nautilus (GNOME's default file manager) to another app. It's clunky, but it's the only option I have.

Luckily, all of the graphic design apps on Linux seems to understand this issue well and implemented their version of the file selection dialog, Blender, Inkscape, GIMP, even LibreOffice, and etc. The only real issue is the web browsers and thus PWAs which are still using the default system file selection dialog.

I hope this issue will be fixed soon.

---

## And some problematic updates

![Burning the Kitchen](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/1nq26l6jshrqv0l1mv9u.jpg)

Think of this as a bonus section. They are working before, but broken now after the system updates. They are as follows:

- ~~I am unable to star any file due to **[GNOME Files issue #2278](https://gitlab.gnome.org/GNOME/nautilus/-/issues/2278)** (the fix is merged but still doesn't land on my system).~~

- ~~The new screen recording tool in GNOME is already broken due to **[GNOME Shell issue #5585](https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585)**.~~ This is fixed in GNOME 43.

- ~~I have to login twice to be able to use my graphic tablet's pen due to **[Mutter issue #2335](https://gitlab.gnome.org/GNOME/mutter/-/issues/2335)**.~~ This is fixed in GNOME 43.

In this sense, Linux doesn't seem like a stable platform as much as everyone would think. At least, from my experience on Windows for more than 10 years, _not_ even once that I had an issue with something as essential to the operating system as the file manager.

> EDIT: as of GNOME 43, all the problematic updates are fixed.

---

This will be the last time I write about issues that I found as a Linux user. Next time, I will write about the features that made me switched from Windows.

Well, this is it for today. Thanks for reading. I hope you guys enjoy my post 🥳

---

**Cover** photo by **[Randy Fath](https://unsplash.com/@randyfath?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)** on **[Unsplash](https://unsplash.com/s/photos/fixing?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)**

**Old man and some retro cams** photo by **[Marc Kleen](https://unsplash.com/@marckleen?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)** on **[Unsplash](https://unsplash.com/s/photos/old-man-bike?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)**

**Stranger Things** photo by **[Puneeth Shetty](https://unsplash.com/@puneeth2?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)** on **[Unsplash](https://unsplash.com/s/photos/sunglasses?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)**

**Scale** photo by **[Vincent Ghilione](https://unsplash.com/@lamoune?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)** on **[Unsplash](https://unsplash.com/s/photos/scale?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)**

**Car Wheel** photo by **[Obi - @pixel6propix](https://unsplash.com/@obionyeador?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)** on **[Unsplash](https://unsplash.com/s/photos/wheel?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)**

**A Man Looking Photos** photo by **[Michal Matlon](https://unsplash.com/@michalmatlon?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)** on **[Unsplash](https://unsplash.com/s/photos/picture-frame?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)**

**Burning the Kitchen** photo by **[lasse bergqvist](https://unsplash.com/@lasse_bergqvist?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)** on **[Unsplash](https://unsplash.com/?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)**