On Arch Linux, Plasma 6.0.1 was released a few minutes ago in the testing package sources.

~~I am curious if this version will reach the official repositories or if there are still reasons to delay an official release.~~

Edit: That went faster than expected. Plasma 6.0.1 has been moved from Testing to Extra.

Here are the things I’ve gathered are non-cosmetic:

Based on https://kde.org/de/announcements/megarelease/6/, I think that many more things are not just purely cosmetic changes.

I must be missing something.

I would say you simply have the wrong expectation that with a so-called mega release a lot of big changes have to happen that the user has to notice immediately. However, many of the changes in Plasma 6 are probably not huge. But many smaller changes are also many changes.

And as others have already written, the changeover to QT 6 was probably not an easy task.

I also see Plasma 6.0 as a basis for things that are planned in Plasma 6.1 or later versions, for example, and are therefore not yet visible to the user. Articles on the development of Plasma are regularly published at https://pointieststick.com, which provide a more detailed insight into the development process.

As always, such statistics should be treated with caution.

What methodology is used to calculate Statcounter Global Stats?

Statcounter is a web analytics service. Our tracking code is installed on more than 1.5 million sites globally.

Source: https://gs.statcounter.com/faq#methodology

It is assumed that there are more than one billion websites worldwide. It is therefore not exactly unlikely that a Linux user will not access any of these 1.5 million websites.

Furthermore, it is quite common for Linux users to use tools such as Pi-Hole that simply block such statistics scripts. This means that these users would not be counted even if they accessed one of these 1.5 million websites. For my part, I also use computers with Linux that I don't use to access websites. Some of these computers don't even have access to the Internet. They are therefore not counted either.

Finally, let's come to the most important point. Percentage values say not much if you don't know the actual number of users behind them. Let's assume, for example, that 3.5 per cent Linux users were detected in December and only 3 per cent in January. However, if the total number of users was higher in January, it is therefore possible that more users were detected in January.

Based on https://docs.atuin.sh/configuration/config/#search_mode, "fuzzy search" is used as standard.

However, one should first read through https://wiki.archlinux.org/title/official_repositories#Testing_repositories and consider whether it is really worth the risk.

For my part, I will simply wait until Plasma 6 arrives in the official package sources.

Nowadays, servers that are not connected to a monitor, keyboard or mouse are often referred to as headless. Regardless of whether they have a graphical user interface (which can be used with tools such as Guacamole, for example).

I'm not trying to say that this is correct, but simply to point out that the term "headless" is now often interpreted differently.

It's more than just a simple tool with which you can tweak audio. Some features are listed at https://valvesoftware.github.io/steam-audio/. The tool is mainly intended for the development of games (also under Linux).

And yes, it's basically just about the fact that Steam Audio is now completely open source.

• Virus scanners only detect a fraction of the harmful programmes.
• Virus scanners can often be tricked.
• Virus scanners often have security vulnerabilities themselves, which are usually quite serious, since such programmes embed themselves quite deeply in the operating system.
• Virus scanners cause many users to become careless because they rely too much on such tools.

Therefore, from my point of view, the disadvantages outweigh the advantages. Therefore, I do not have such a tool permanently installed, neither under Linux nor under Windows. However, every 6 months I scan my Windows installation with a USB-bootable virus scanner. No actually harmful programme has been found for years.

In my opinion, the following things are much more important than any security software.

• Install updates as soon as possible. Under Windows, you can use tools like Chocolatey for this.
• Only install software from trustworthy sources.
• Only install software that you really need.
• Only use root or administrator rights if you have to. For everything else, the rights of the user account are sufficient.
• Create backups regularly.
• Think before you act.

Especially the last point is a problem for many users. I can't tell you how many times I've witnessed someone receiving an alleged invoice from mobile provider A by email and opening it, even though they had a contract with provider B.

Ran sudo pacman -Syu; sudo pacman -Syy like I do every few days

Syy forces the package database to be updated even if no updates are available.

In my opinion, this makes no sense, especially after you have already run pacman -Syu before. Basically, you only generate additional, unnecessary traffic on the mirror you are using. Pacman -Syu is normally always sufficient.

The journal was really long so I moved past it

The display of the systemd journal can be easily filtered. For example, with journalctl -p err -b -1, all entries of the last boot process that are marked as error, critical, alarm or emergency are displayed.

Has anyone else ran into this issue when updating?

Not me. But other users do. Some of them also use a distribution other than Arch (or a distribution based on it). When I look at the problems, the current kernel is probably quite a minefield as far as problems are concerned.

Any advice for preventing future crashes or issues like this so I don’t fear updating?

As other users have already recommended, you could additionally install the LTS kernel. And if you use BTRFS as a file system, create snapshots before an update (https://wiki.archlinux.org/title/snapper#Wrapping_pacman_transactions_in_snapshots).

And it should be obvious that important data should be backed up on a regular basis.

When it comes to SBC, the choice has always been a Raspberry Pi. Why? A Raspberry Pi may not have the best performance. But in return you can be sure that it will still be supported after a kernel update. And that is exactly the problem with many alternatives. They support a certain, mostly old, kernel. And that's it. Furthermore, the community around the Raspberry Pi is simply huge.

• Create interesting content on your Lemmy instance.
• Participate in discussions on your Lemmy instance.
• Tell friends and acquaintances about Lemmy without missionizing.
• Create for example content on your blog that points to Lemmy.

All this should be much more useful than doing anything on Reddit.

You can follow the submissions via an RSS feed.

For example, if you use the link Https://lemm.ee/feeds/u/Corr.xml?sort=New, all your previous posts will be displayed.

Instead of lemm.ee you need to specify the instance where the user in question is registered. And instead of Corr you have to enter the username. For example https://discuss.tchncs.de/feeds/u/fryboyter.xml?sort=New. That would be in this case my contributions.