Arch Linux User Repository

@SolarAquarion I see what the issue is… The malicious prior maintainer didn't just add a tracker to the install script (see comments on 2025-11-04)… He also broke the install script. This package hasn't been properly registering its ownership of /usr/share/glib-2.0/schemas/gschemas.compiled with pacman as a result of a change he made the day after he added the tracker. I just pushed an update that restores the install script to its state prior to the malicious maintainer's modifications of it.

Unless I'm mistaken, if you run pacman -Qo /usr/share/glib-2.0/schemas/gschemas.compiled, you'll be informed that the file has no owner. If that's the case, to upgrade this package to the version I just released, you'll need to upgrade the package with the following flag provided to pacman:

--overwrite /usr/share/glib-2.0/schemas/gschemas.compiled

The other option is to simply rm that file prior to upgrading this package and immediately upgrade it, since it's meant to be owned by this package anyway.

Thanks for the heads up on this.

error: failed to commit transaction (conflicting files) mate-menu: /usr/share/glib-2.0/schemas/gschemas.compiled exists in filesystem Errors occurred, no packages were upgraded.

Update: Applied the relevant patches (much later than intended). It seems likely that Ubuntu MATE will receive a 26.10 release, and quite a few more changes have been made to the upstream repository in preparation for that. I'll be sure to update the package here once more as soon as there's a new official release.

I checked the upstream git repository, and there have been three commits since the last release. I normally wouldn't include them in a non-git AUR package, but they're all security-relevant bug fixes, including two memory leaks and an issue wherein the launch directory of applications could change to an unintended value. If there are no objections from users to including the three commits in question as patches, I'll do that over the weekend.

Why was there a tracker in this package ?

Malicious action from the current maintainer. This is now reverted, and the account has been banned. We will accept the pending orphan request for this package as soon as it can be accepted, so the package should be free for adoption after that.

I'm happy to promote someone as co-maintainer in the mean time if anyone is interested to jump in before that.

Why was there a tracker in this package ?

FYI the python problem occured again, this time to 3.9

for myself, I solved it by symlinking the mate-menu folder into the 3.9 site-packages directory and now it works again (also, that caused about twenty mate-menus to appear in my panel, since I had tried adding it ... often)

@dmftradutor: clean you aur package cache. If you're using yay, do a yay -Sc and accept all cleaning question.

I'm trying to update mate-menu 20.04.1-2 to 20.04.3-1 but it fails sha256sums validation test. So it fails to compile mate-menu.

What is the solution for this?

Since 20.04.1 python-unidecode is no more a dependency.

Other solution is to install https://aur.archlinux.org/packages/python37/ Or use downgrader to python version 3.7 + block package