I’m experiencing an issue with activating wireguard connections via plasma-nm.
I get 2 error messages when trying to activate the wireguard connection from Networks:
Connection xxx deactivated
The device could not be configured.
I can activate a wireguard connection from cli, but if the connection was created in the Connections dialog, I get the error messages. Plasma-nm 126.96.36.199 works with wireguard-arch 0.0. 20190702-2, but it broke when going to wireguard-arch 0.0. 20190702-3 and continues in wireguard-arch 0.0. 20190702-4.
Any suggestions on how to troubleshoot this problem?
After a recent update, smb4k will start, but no gui.
Operating System: Antergos Linux
KDE Plasma Version: 5.14.5
Qt Version: 5.12.1
KDE Frameworks Version: 5.55.0
Kernel Version: 4.20.7-arch1-1-ARCH
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-6820HQ CPU @ 2.70GHz
Memory: 3.8 GiB of RAM
You, my friend, are brilliant!
VMware 3D graphics was the issue. Unchecking the option fixed the crash.
I looked further at the VMware documentation and discovered:
Accelerate 3D graphics
Select this setting if you run applications that use DirectX 9 or DirectX 10 accelerated graphics. Accelerated graphics capabilities apply to Windows XP or later guests on hosts running Windows or Linux.
The virtual machine must be a Workstation 6.x or later virtual machine and must have VMware Tools installed from Workstation 7.x or later.
So, checking the options provides not benefit for Linux guest.
Odd problem here folks. I am running a Windows 10 host, VMware Workstation 15.1 and Antergos KDE.
When mesa upgraded from 18.2.6-1 to 18.3.1-1, every time I run Chomium [Version 71.0.3578.98 (Official Build) Arch Linux (64-bit)] and attempt to login to Gmail, when I attempt my password, the entire VM crashes. This happens on Falkon [Application version 3.0.1 QtWebEngine version 5.12.0] as well. Any thoughts?
I’m going to stay with Mesa 18.2.6-1 for the moment.