Plasma 5.21 Beta preview is up and running on my production machine.
No issues found so far, and I really like the updated application launcher.
If you cannot wait until the official release on Feb 16th, you can get testing this update today by making a minor tweak to your pacman.conf file.
Open /etc/pacman.conf as root and uncomment any “testing” references.
Just above the first entry for testing, add the following, save and then run an update via sudo pacman -Syu
[kde-unstable]
Include = /etc/pacman.d/mirrorlist
Reboot and you should see the updated wallpaper to know you are now on the 5.21 beta build.
I think they want to make W10 users more welcomed and relaxed with the transition to Linux. Aside from Linux Mint and Cinnamon, I can see Plasma being the dominate DE of 2021.
I agree. I used to run Linux Mint Cinnamon and i always used to run every current and RC kernel and never had an issue. I currently use mostly KDE because it’s very smooth/fluid and quick response. I would like to see better Icon support. That is where i find the most issues. I have EndeavourOS KDE, Xfce and Cinnamon running on one machine with rEFInd.
Question, on this pc i have Arch/Plasma and on my main pc i have EOS Xfce. To install Arch/Plasma i used archfi, how do i tell IF im using wayland or xorg? I think both were installed at time of installation IF i remember correctly lol. So IF wayland goes all wonky it defaults to xorg? But I think in the near future I’ll only be using Plasma i like it that much. Thanks @robinjuste for explaining how to install Plasma 5.20.90
The rollback solution I listed is from the Arch wiki site, so I’d say to run this whilst logged in as root, or via the sudo command. Either way, you will get an prompt if you need to use sudo.
The issue with your command wasn’t sudo, it should have the yy pacman flag and not the y flag, forcing a package databases refresh when changing repos.
When an Arch wiki command has # as the command prompt root access is implied (ie sudo), when $ normal user access is implied.
This is very rarely the case, and in nearly all cases not recommended.
-y, --refresh
Download a fresh copy of the master package database from the server(s) defined in
pacman.conf(5). This should typically be used each time you use --sysupgrade or -u. Passing two
--refresh or -y flags will force a refresh of all package databases, even if they appear to be
up-to-date.
I would think it seems that only -y would be enough since it will download “a fresh copy of the master package database from the server(s) defined in pacman.conf”. Wouldn’t that be enough?