@Yochanan Strictly speaking, my last post is not related to DKMS vmware problems and could potentially affect other applications using xwayland , not just vmware , so I wrote about it here to pay attention if the problem affects other areas. In any case use this information as you see fit
1 Like
┬─┬ ノ( ゜-゜ノ)
1 Like
Hi,
Plasma 6.5.0 landed on unstable branch, welcome 
5 Likes
Really happy to have gotten Plasma 6.5.0. Loving it; so far so good!
4 Likes
No issue so far with Plasma 6.5.
I just purged my system of anything depending on gtk2. It’s been EOL for about 5 years and Arch is very actively removing mostly everything depending on it as we speak. Quite a few packages have already been dropped to the AUR.
References:
3 Likes
Yup, I jumped in 4 days ago and had only one issue with Conky being stuck on a single desktop, so I had to make a window rule instead (i.e. Sticky doesn’t work any more).
steam-native-runtime package will need some gtk2 packages. So Arch might remove it at some point from their repos …
I just ran into this issue as my install has unresolved updates for the following:
lib32-libappindicator-gtk2, lib32-libindicator-gtk2, libindicator-gtk2
These are only showing in AUR now and are required for steam-native-runtime. When I try to update them the builds fail. I use Steam, obviously, and am not sure what the path forward is.
Remove steam-native-runtime as it won’t be supported anymore. Remove GTK2 from the official repositories - Arch-dev-public - lists.archlinux.org
3 Likes
Thank you. That solved my update issue and removed 75 packages from my system in the process.
That’s now removed from the repos along with gtk2 and anything depending on it.
The gtk2 purge is now complete.
As @philm likes to say, “Please let us know if we missed something”. 
3 Likes
6 posts were split to a new topic: Not all the gtk2 files have yet been removed from the repos
2 posts were merged into an existing topic: KDE Plasma 6.5 Officially Released, This Is What’s New
Updated an HP ENVY x360 Convertible 13-ar0xxx system with LUKS encryption. On kernel 6.17.6, if I execute the reboot command, after the system reboots, the keyboard is disabled and I cannot enter a decryption password. If I instead execute poweroff , wait for the system to power down, and then use the physical power button to power on the system, the keyboard works fine and I can enter a decryption password. Switched to testing branch and the keyboard problem on reboot disappears. Odd.
1 Like
Are you multi-booting with Windows?
If you are, this is only relevant if Fast Startup is activated; however, it must be disabled when multi-booting with Linux.
The procedure: From within Windows, open an Administrative CMD/PowerShell prompt, and enter powercfg /h off. That’s it.