Yes, it’s nice to have that VM back alive. I somehow like the history of it.
The thing that triggered looking at that file was a line on the VMware page of https://wiki.manjaro.org:
There are no special requirements to installing Manjaro on VMWare. open-vmware-tools is pre-installed. It should “just work”.
NOTE: I had to install the open-vm-tools, the package was not installed in the fresh new VM.
And because I had this fresh VM with current Manjaro KDE installed, which worked out of the box, I decided to look in the /etc/X11/mhwd.d folder and it was empty.
It took a while before I figured out how to investigate symlinks…
So, the path is not a symlink:
hvroon@HanManjaro ~]$ namei /etc/X11/mhwd.d/vmware.conf
f: /etc/X11/mhwd.d/vmware.conf
d /
d etc
d X11
d mhwd.d
- vmware.conf
[hvroon@HanManjaro ~]$
And the file is a real file (it doesnt start with “l”):
[hvroon@HanManjaro ~]$ cd /etc/X11/mhwd.d
[hvroon@HanManjaro mhwd.d]$ ls -l
total 4
-rw-r--r-- 1 root root 613 26 feb 2018 vmware.conf
[hvroon@HanManjaro mhwd.d]$
I found three manjaro.conf files with KFind:
manjaro.conf usr/lib/sysusers.d
manjaro.conf usr/lib/tmpfiles.d
manjaro.conf usr/share/systemd/bootctl
None of them look like the vmware.conf file if that is relevant. Strange, three files with the same name on different locations.
This is the content of vmware.conf:
##
## Generated by mhwd - Manjaro Hardware Detection
##
Section "Device"
Identifier "Device0"
Driver "vmware"
Option "DRI" "true"
EndSection
Section "DRI"
Group "video"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
EndSection
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
Section "Monitor"
Identifier "Monitor0"
DisplaySize 444 258
EndSection
Luckily it was created by “Manjaro Hardware Detection” on Febuary 26th, 2018, and not by me 
You may be interested in the first section I asume?
At the bottom left on the logon screen it says: Desktop session: Plasma (X11)
The reason why I wanted this 10-monitor.conf file was because I liked a specific resolution not listed in Display & Monitor, Resolution dropdown. So I had to drag the VM window after every startup because communication between VMware Player and linux open-vm-tools is not as extended as between VMware player and Windows VMware tools, where the VM remembers the size it was dragged to.
I have notes that I used old wiki pages and a package xorg-xrandr to produce the info needed for this config file. After producing the needed info I went back to a backup from before installing xorg-xrandr because it was not needed anymore, back then.
The contents of my 10-monitor.conf file:
Section "Monitor"
Identifier "Virtual1"
Modeline "1680x974_60.00" 135.75 1680 1784 1960 2240 974 977 987 1011 -hsync +vsync
Option "PreferredMode" "1680x974_60.00"
EndSection
When looking at Display configuration, the identifier (I asume it is) in the screen says “Virtual-1”.
What if I use that name in the config file, so add the dash?
→ Yes, it works after reboot! Just had to select the new resolution 1680x974 in Display configuration Resolution dropdown.
What I did today is start with the VM version that had the 364 updates from between June 13th and July 8th installed. Then clean the cache and install the updates from July 12th.
I try to keep the amount of updates as low as once a month at the most, so that the virtual disk doesn’t grow unnecessary. With a Windows VM the disk kan be compacted to get the air out, with this Linux VM that doesn’t work. The smaller the VM, the quicker backups are made is the reason for keeping it small.
After the updates I will go through your posts to replace vlc-nightly and then cleanup the alien packages. It seems a good idea to do that to avoid some future problems.
And read more about pamac, pacman and the Add/remove software (which seems the GUI for pamac).
Since you let me do everything with pacman, I want to look into what is the best to do for updates.
I don’t use AUR packages as far as I know.
Best regards