Error during garuda update after install

After installing the gaming addition from the 230501 iso, on initial start the garuda assistant starts as normal but fails. The output is as follows:

: Synchronizing package databases...
garuda is up to date
extra                                   8.3 MiB  5.11 MiB/s 00:02 [------------------------------------] 100%
multilib is up to date
chaotic-aur                             2.5 MiB  5.00 MiB/s 00:00 [------------------------------------] 100%

--> Refreshing mirrorlists using rate-mirrors, please be patient..🍵
:: Synchronizing package databases...
garuda downloading...
core downloading...
extra downloading...
multilib downloading...
chaotic-aur downloading...
:: Starting full system upgrade...
:: Replace mangohud-common with extra/mangohud? [Y/n] y
:: Replace qgpgme with core/qgpgme-qt5? [Y/n] y
warning: reflector-simple: local (2.0-1.1) is newer than garuda (2.0-1)
resolving dependencies...
looking for conflicting packages...
warning: removing 'python-xdg' from target list because it conflicts with 'python-pyxdg'
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: mangohud and mangohud-common are in conflict
Press enter to exit:

I have reinstalled but the same problem occurs. I've also looked for this or a similar error and haven't found one. I have also installed on this machine before. The only difference is going from 32GB ram to 64GB.

Thanks in advance for the assistance.

From what I can find, it looks like the python-xdg/python-pyxdg conflict is an old thing:
AUR (en) - python-xdg (comments)
Why do python-pyxdg and python-xdg conflict?
I think you'll need to find out which installed packages need them, maybe you'll have to install one or more in a Python virtual environment "the Python way" rather than using system packages.
I'm not sure if there are default packages depending on them in the gaming edition, I see I have python-pyxdg on my (Sway WM) box and it was pulled in by bpython which I installed myself.
In case ytmdl is involved, maybe try yt-dlp instead.

1 Like

Hi there, welcome to the forum!


Thanks very much. I really appreciate it. I just couldn't figure out on a fresh install that had worked in the past on a clean disk would suddenly have this problem. Again, I really appreciate the help from all who replied.

Try ISO from 23-05-03

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.