Xserver not starting after updates in VMware VM

Support Virtualization
1

Hello,

I have a bigger problem with my just-for-fun Manjaro VM.
After updating yesterday (July 9th) and rebooting the screen stayed black with one line on top:
/dev/sda1: clean, 358068/1966080 files, 3046484/7864063 blocks

Running in VMware Workstation 17 Player 17.6.3

Before updating:
KDE PLasma: 6.3.5
KDE Framework: 6.14.0
Qt: 6.9.0
Kernel: 6.12.28-1 Manjaro 64 bit
Graphics: X11

After updating:
KDE PLasma: 6.3.5
KDE Framework: 6.15.0
Qt: 6.9.1
Kernel: 6.12.28-1 Manjaro 64 bit
Graphics: X11

This is something I cannot solve myself, even after reading a couple of posts.
The post that seems to describe the problem:

In that post linux-aarhus points to an archlinux forum topic where I get lost without specific linux skills. I cannot figure out which dependencies are involved, and don’t have the skills to try and uninstall packages and get older versions from somewhere to replace them.
I only figured out how to get to the console and find the Xorg.0.log lile.

Does whatever is updated, and whatever will not be updated, mean that this VM will not run anymore or I have to stop updating it? Or will it be solved by upstream arch updates?

If I can repair things and someone has an idea of what I need to do?

I have the following available:

  • Three versions of the VM:
    Before updates (last updated June 13th)
    After update but suspended (not rebooted)
    Updated version (that only is accesible after pressing Ctrl-Alt-F2.
  • An Xorg.0.log file from before the updates
    (without errors regarding “screen”)
  • An Xorg.0.log file from after the updates
    Containing
[    21.022] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[    21.022] (EE) Failed to load /usr/lib/xorg/modules/drivers/vmware_drv.so: libxatracker.so.2: cannot open shared object file: No such file or directory
[    21.022] (EE) Failed to load module "vmware" (loader failed, 0)
[    21.022] (EE) No drivers available.
[    21.022] (EE) 
Fatal server error:
[    21.022] (EE) no screens found(EE)
  • A large pacman.log with updates back to 2018.
  • A list of all installed packages (pacman -Q)

Please let me know if I need to upload one of the files if someone wants to help.

Reagrds, Han

2

Hi @HanVroon,

I think that’s your problem. Try the VM before the update and check what kernel it runs:

mhwd-kernel --list

It might be that the kernel got updated but not the module…

3

Hi,

Isn’t that the kernel versions I mentioned above in Before/After updating?
Anyway, the output is:

mhwd-kernel --list
available kernels:
* linux510
* linux515
* I inux54
* linux61
* linux612
* linux615
* linux616
* linux66
* linux61-rt
* linux612-rt
* linux613-rt
* linux614-rt
* linux615-rt
* linux66-rt

While posting, the forum engine pointed me to a similar topic:

It doesn’t look like the same problem though.

4

I don’t know why mhwd-kernel --list shows so many, when I enter mhwd-kernel -li I only get linux612 (which seems right (Kernel: 6.12.28-1 Manjaro 64 bit)

1 Like
5

Humble apologies. My mistake. You are, indeed, correct. So now, from that working snapshot, please run:

pacman -Qs vmware
6

Because I made a mistake. The correct command is:

mhwd-kernel --listinstalled

--list shows the kernels available.

1 Like
7

Sorry for the delay, had to figure out how to pipe output to my shared folder on the host in a textfile, better copy/paste.

local/open-vm-tools 6:12.5.2-1
    The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools
local/xf86-input-vmmouse 13.2.0-2 (xorg-drivers)
    X.org VMWare Mouse input driver
local/xf86-video-vmware 13.4.0-3 (xorg-drivers)
    X.org vmware video driver
8

Looked in the update output for open-vm:
Download of open-vm-tools (6:12.5.2-2) started
Download of open-vm-tools (6:12.5.2-2) finished
Upgrading open-vm-tools (6:12.5.2-1 → 6:12.5.2-2)…

9

OK, my day is ending here, in South Africa. It’s just before 5pm, and I have to go soon.

What I will recommend, however, is comparing the modules or anything vmware-related installed on the working installation, with the broken one, because obviously something is wrong there.

Another option is creating another copy of the working VM, doing the update on that and seeing if the same happens.

10

I’ve done that several times already. With 3D acceleration enabled/disabled, with a custom 10-monitor.conf file present/removed, with mesa (which seems to be involved?) unchecked in pamac, a.s.o.

Since I don’t understand the other topics dealing with similar problems recently (as reffered to above), I cannot think of anything clever to do. In linux world I’m a user, not an admin (as I am in MS’s world).

I thought to find out how to go back to the previous open-vm-tools package, but perhaps I don’t understand even that :slight_smile:

# cd /var/cache/pacman/pkg
# find —type f —name "open-vm*"
./open0vm-tools-6:12.5.2-2-x86_64.pkg.tar.zst.sig
./open0vm-tools-6:12.5.2-2-x86_64.pkg.tar.zst
#

I thought this path contains the previous package, that I should install with…

# pacman -U file:///var/cache/pacman/pkg/*package*-*old_version*.pkg.tar.*type*

…as per an archlinux wiki page.

Find gives me back the same version number as newly installed, I was expecting a “6:12.5.2-1” file.

11

As you can read from the topic referenced - the xf86-video-vmware package has been removed from the repo.

You would also have noted that I tested a fresh xfce in a vmware virtual machine.

I listed the packages from that installation using pacman -Qqm and uploaded to https://0x0.st/8DJl.txt

A package is never removed from the repo without good reason - especially the Arch repo.

This only happens when the functionality provided by the package is obsolete or provided by a newer package.

If I were in this situation - I would remove the packages you listed - as they may not be required - as a bare minimum remove xf86-video-vmware - it is obsolete.

If the issue persist - I would remove plymouth from the equation.

I would also list all alien packages - third party packages - either built on purpose or removed from the repo.

pacman -Qqm

Pipe it to a file for later reference

pacman -Qqm > alien-pkgs.txt

Remove them all

sudo pacman -Rns  $(pacman -Qqm)

Run pacman-mirrors --status and verify the first mirror is up-to-date. If not run pacman-mirrors --continent to rebuild your mirror list.

When that is in place - do a full system sync - the system may be up-to-date - then it is just a verification

sudo pacman -Syu
12

Hello,
Thanks for all the suggestions so far.
I tried to do what you suggested, in order.

pacman -Rs xf86-video-vmware
pacman -Rs xf86-input-vmmouse
pacman -Rs open-vm-tools

Packsages where removed with ending message:

Reloading system manager configuration...
Reloading device manager configuration...
Arming ConditionNeedsUpdate ...

After reboot:

[FAILED] Failed to mount /mnt/hgfs .
[DEPEND] Dependency failed for Local File Systems .
(expected, this is about VMware shared folders that don't work anymore)

I didn’t do anything with “remove plymouth from the equation”, I did not understand what you mean, plymounth is not an installed package in the list (pacman -Q output).

pacman -Qqm output before and after removing the packages:


attica-qt4
breeze-kde4
cantata
gnome-icon-theme
gnome-icon-theme-symbolic
gtk-theme-breath
ipw2100-fw
ipw2200-fw
kdelibs
libdbusmenu-qt4
manjaro-documentation-en
manjaro-firmware
manjaro-hotfixes
manjaro-settings-manager-kcm
microsoft-office-web-jak
networkmanager-dispatcher-ntpd
oxygen-kde4
pcmciautils
phonon-qt4
phonon-qt4-gstreamer
polkit-qt4
pulseaudio-ctl
pyside2
python-jade-application-kit
python-shiboken2
qt4
reiserfsprogs
sni-qt
systemd-kcm
transcode
vlc-nightly
xdg-su
xf86-input-keyboard
xf86-input-mouse
xf86-video-vmware  (after removing three vmware packackes this package was not present with pacman -Qqm)
zd1211-firmware

The pacman -Rns $(pacman -Qqm) didn’t work:

# pacman -Rns  $(pacman -Qqm)
# pacnan —Rns $(pacnan —Qqm)
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing vlc—nightly breaks dependency 'vlc' required by phonon—qt6—vlc

Then came the result of removing the open-vm tools I think:

# pacman-mirrors --status
:: Dounloading status failed!
:: Please check you network connection

Then I started over with the pre-updates VM
In the pamac GUI I unselected packages that might be involved:

image
image801×149 11.8 KB

Same result, slightly different error in /var/log/Xorg.0.log:
(libLLVM.so.19.1 instead of libxatracker.so.2)

Failed to load /usr/lib/xorg/modules/drivers/vmware_drv.so: libLLVM.so.19.1: cannot open shared object file: No such file or directory

There seem to be a lot of dependencies involved and I’m certainly not the one who is going to figure that out.
I have this VM for more than 7 years now, the only thing that I ever did regarding packages was installing kdenlive and kio-admin. The rest is rolling release. Done with Octopi, and lateron with Pamac (both GUI).
But, maybe even Manjaro doesn’t roll forever, especially if it runs in VMware player.
Which linux fan wants to run linux in a VM on a Windows host anyway :slight_smile:

Because of my user-level knowledge it might be better to start all over. See if all my documentation on how the current interface was configured is enought to get my Manjaro VM back from scratch.
It feels like having lost, but starting fresh can be a good idea. After all I never had a Windows system running for seven years :slight_smile:

I downloaded manjaro-kde-25.0.4-250623-linux612.iso and it runs, didn’t install yet.
The only thing that I am afraid of is that with the lack of open-vm-tools I will not be able to exchnge data between host and client via the shared folder offered by VMware. I don’t mind missing copy/paste.

13

The only package I did know was removed from the repo and therefore must be obsolete was xf86-video-vmware

The other was merely a suggestion to see if it made any change.

plasma desktop depends on vlc but we no longer use the nightly version so replace the nightly with the standard vlc package and add back your open-vm-tools - you should be notified that vlc conflicts with vlc-nightly - accept the replacement…

sudo pacman -Syu vlc open-vm-tools

Then run the command to remove aliens alien packages - this time I expect it to go through

15

OK, I proceeded… here is what I did.

By the way, I do all commands without sudo, because after I press Ctrl-Alt-F2 to get a prompt I login as root, no reason not to? I assume that all commands are system wide, not user specific.

Removed the video driver with pacman -Rs xf86-video-vmware
Then did a reboot to be sure.

Then forced package installation with: pacman -Syu vlc open-vm-tools
Gave y to replace and proceed.
It looked like half of the system was downloaded, much more than a screen full of package names came by. At the bottom it said:

Total Download Size:  1354,98 MiB
Total Installed Size: 3329,31 MiB
Net Upgrade Size :    -388,59 Mib

Did NOT reboot then.
Then removed the “aliens” with predator: pacman -Rns $(pacman -Qqm)
Because of additiona;l dependency messages see screenprint below:

image
image1285×304 8.78 KB

Then did a rebot, still stuck on the /dev/sda1: clean screen

Then I did: pacman-mirrors --status
The first mirror was Netherlands, so seemed good.
Still did (to be sure?): pacman-mirrors --continent
After that: sudo pacman -Syu, had nothing to do.

Still stuck on the /dev/sda1: clean screen.
The contents of the Xorg.0.log file is different now:

[    22.050] (--) Log file renamed from "/var/log/Xorg.pid-973.log" to "/var/log/Xorg.0.log"
[    22.053] 
X.Org X Server 1.21.1.18
X Protocol Version 11, Revision 0
[    22.053] Current Operating System: Linux HanManjaro 6.12.37-1-MANJARO #1 SMP PREEMPT_DYNAMIC Thu, 10 Jul 2025 15:37:43 +0000 x86_64
[    22.053] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64 root=UUID=48dd3a98-27df-4664-b4d6-6ed96a2b99c8 rw quiet udev.log_priority=3
[    22.053]  
[    22.053] Current version of pixman: 0.46.2
[    22.053] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    22.053] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    22.053] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 13 10:31:40 2025
[    22.054] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    22.054] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    22.054] (==) No Layout section.  Using the first Screen section.
[    22.054] (==) No screen section available. Using defaults.
[    22.055] (**) |-->Screen "Default Screen Section" (0)
[    22.055] (**) |   |-->Monitor "<default monitor>"
[    22.055] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    22.055] (**) |   |-->Device "Device0"
[    22.055] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    22.055] (**) Allowing byte-swapped clients
[    22.055] (==) Automatically adding devices
[    22.056] (==) Automatically enabling devices
[    22.056] (==) Automatically adding GPU devices
[    22.056] (==) Automatically binding GPU devices
[    22.056] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    22.056] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    22.056] 	Entry deleted from font path.
[    22.056] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    22.056] 	Entry deleted from font path.
[    22.056] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    22.056] 	Entry deleted from font path.
[    22.056] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    22.056] 	Entry deleted from font path.
[    22.056] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF
[    22.056] (==) ModulePath set to "/usr/lib/xorg/modules"
[    22.056] (**) Extension "Composite" is enabled
[    22.056] (**) Extension "RENDER" is enabled
[    22.061] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    22.061] (II) Module ABI versions:
[    22.061] 	X.Org ANSI C Emulation: 0.4
[    22.061] 	X.Org Video Driver: 25.2
[    22.061] 	X.Org XInput driver : 24.4
[    22.061] 	X.Org Server Extension : 10.0
[    22.064] (++) using VT number 2

[    22.064] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    22.070] (II) xfree86: Adding drm device (/dev/dri/card0)
[    22.070] (II) Platform probe for /sys/devices/pci0000:00/0000:00:0f.0/drm/card0
[    22.103] (--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 0x????????/131072
[    22.103] (II) LoadModule: "glx"
[    22.104] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    22.109] (II) Module glx: vendor="X.Org Foundation"
[    22.109] 	compiled for 1.21.1.18, module version = 1.0.0
[    22.109] 	ABI class: X.Org Server Extension, version 10.0
[    22.109] (II) LoadModule: "vmware"
[    22.110] (WW) Warning, couldn't open module vmware
[    22.110] (EE) Failed to load module "vmware" (module does not exist, 0)
[    22.110] (EE) No drivers available.
[    22.110] (EE) 
Fatal server error:
[    22.110] (EE) no screens found(EE) 
[    22.110] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    22.110] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    22.110] (EE) 
[    22.110] (EE) Server terminated with error (1). Closing log file.

I have to stop for today, will continue tomorrow.
Maybe I should try removing vlc-nightly and then remove “aliens” on the VM version BEFORE the last monthly updates and then update?
So far I have done all suggestions above on the “stuck” VM version.

16

That is correct

vlc-nightly was replaced by vlc when you executed the sync command.

The reason you got a lot more - is caused by the latest stable snap on 2025-07-12

[Stable Update] 2025-07-12 - Kernels, Systemd, GNOME, NVIDIA, Plasma, Firefox, VLC splits - #2 by discobot

This message can be safely ignored.

With vmware you choose a base configuration targeting a specific kernel series when you intend to install an unsupported Linux.

Since it is 7 years the kernel could have been 4.x or 5.x.

It seems to be solely graphics related but I cannot know.

If you can access the system without the login manager - I would try to disable lightdm so I would at the very least be able to have an actual running instance using console only.

To disable display manager

systemctl disable --now lightdm

This should make it possible to boot the system to console.

17

I already had a running console with Ctrl-Alt-F2 after the /dev/sda1 message.
That’s how I did everything you suggested.

And with systemctl disable --now lightdm I get the message:
Failed to disable unit: Unit lightdm.service does not exist

I did my last attempt to get the original VM updated and running, inspired by a topic post where someone wrote “I fixed my problem by downgrading mesa-1:25.1.1-1 to mesa-1:25.0.5-1 and xf86-video-vmware 13.4.0-4 to xf86-video-vmware 13.4.0-3:”

  • Started with the original VM, last updated June 13th.
  • Replacend vlc-nightly with: sudo pacman -S vlc
  • Checked the old versions of involvend packages:
pacman -Qs mesa
pacman -Qs vmware

Tried to add a correct line to /etc/pacman.conf, but that did not work as I noticed later:

IgnorePkg = mesa vmware

Did an update with sudo pacman -Syu

Rebooted, logged in after Ctrl-Alt-F2.
Checked the packages mesa and vmware and saw that they were updated despite IgnorePkg.
Then found a way to downgrade, and downgraded all the packages that were updated:

pacman -S manjaro-downgrade
manjaro-downgrade mesa
manjaro-downgrade lib32-mesa
manjaro-downgrade lib32-mesa-demos
manjaro-downgrade mesa-demos
manjaro-downgrade mesa-utils
manjaro-downgrade open-vm-tools

Each time choosing the exact version that I had before upgrading form the list.

And still no Xserver. I don’t think that this problem gets solved.
I will keep the VM in a state of June 13th 2025 for as long as I want.
And start with a new VM as mentioned above.
But not any time soon, enough Manjaro, it’s Summer on this side of the globe.

Thanks for the help, hopefully I have more solvable questions next time :slight_smile:

18

BIG EDIT:

I decided to do one last thing:
Compare the /etc/X11 directories on both the fresh installed VM (installed with manjaro-kde-25.0.4-250623-linux612.iso) and the old updated VM where Xserver doesn’t start.

Actually I copied bot X11 directories to the Windows share and compared them with tooling that I an familiar with. Most file were the same.

There was one difference, in the old structure the subdir mhwd.d contained a vmware.conf, on the new VM this file was absent.

So I deleted that vmware.conf and rebooted. Desktop back :slight_smile:

For some reason the monitor file with my preferred resolution (/etc/X11/xorg.conf.d/10-monitor.conf) is now ignored, but maybe I will figure out how to get that bag without dragging the VM window every time I start Manjaro.

1 Like
19

One more thing I want to mention in this Manjaro in VMware topic:

Since a couple of months I have huge keyboard lagging in the VM.
That was very annoying the last days having to work in a terminal session with commands. Numerous thimes I had to wait until the keyboard buffer was empty after hitting the arrow keys too long.
Today I found the solution, search for " Experiencing keyboard lag/input delay on any Linux Distribution". It also mentions an option to enable Virtualize IOMMU in the VM CPU properties (didn’t try that).

Ad the following line to the .vmx file of the VM:

keyboard.vusb.enable = "TRUE"
20

Yes :man_facepalming: - my fault - I don’t know why - but I completely missed the fact that you are using Plasma - I was thinking Xfce - perhaps because a similar issue was about Xfce.

It is great that you narrowed it down and have the VM running again.

I got curious - it is a puzzle to solve - and I cannot help it - but I have to try - because I personally use vmware - even given the unsupported nature - I have to support myself.

//EDIT:
I believe the vmware.conf is an old configuration which has survived until it caused the system to fail.

What is the content of said file? Was it symlinked into /etc/X11/xorg.conf.d as manjaro.conf?

If it is referencing the vmware driver - it explains the topic you referenced when creating this topic.

Please check - lower left corner of you login window - is it

  • Plasma Wayland session
  • Plasma X11 session

Because Plasma Wayland session does not use the configs in /etc/X11

If you have a preferred display resolution - use System Settings → Display & Monitor to set the display size.

21

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 :slight_smile:
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

1 Like