I'm running Parallels Pro 20.2.1 (55876). I used Fedora-Everything-netinst-aarch64-41-1.4.iso to set up two almost identical VMs, the only difference being that one uses Gnome and the other the Cinnamon spin. I used the default package selection proposed by the Fedora installer in both cases. Both VMs were configured at install with an identical sudoer user and with the same shared Mac folders. After install, Parallels Tools successfully installed in both VMs. As of this writing, both kernels are the same version (6.13.4-200.fc41.aarch64). The problem I'm facing is that Parallels shared folders do appear under /media/psf but are inaccessible in the Gnome VM, while they work as expected in the Cinnamon VM. In the Gnome VM, the permissions on folders within /media/psf are set to root:root with bits of 700. In the Cinnamon VM, the permissions on the same folders are set to sudoer:sudoer with varying bits depending on the folder (unsure why this is not uniform). The end result is that shared folders appear with a lock icon in Gnome's Files app. Double-clicking a locked folder triggers a prompt for sudoer's password which, when entered, opens an empty folder (there is content there on the Mac side). Copying a file in the folder on the Fedora side doesn't throw an error, but the file doesn't appear on the Mac side. Meanwhile, in the Cinnamon VM, the contents of shared folders show as expected in Nemo, and files/folders can be created/copied without issue both on the Mac side and on the Fedora side. In the Gnome VM, I did a sudo chown -R sudoer:sudoer on a dummy shared folder that contains files on the Mac side, but it still opens empty in Fedora, and the owner change doesn't persist between reboots anyway (permissions revert to root:root on their own). I'm not sure if this is related, but I also tried to reinstall Parallels Tools from the Actions menu in the Gnome VM, and the operation fails (this seems to have been reported a couple of times in the forums recently and I can provide installer log if it seems relevant), though the tools successfully reinstall on their own after a kernel update. Not sure what's happening here. I'm hoping someone can provide a couple of pointers. Many thx.
