Description of problem: After a live or a network install of Fedora 32 Beta virtual guest, a folder shared by VirtualBox is mounted but is not accessible. Version-Release number of selected component (if applicable): anaconda-32.24.2-3.fc32 How reproducible: Always Steps to Reproduce: 1. Perform network install of Fedora 32. 2. Log in as new standard user. 3. Try to open shared folder mounted by VirtualBox. Actual results: Access is denied due to missing permissions. Expected results: The shared folder can be accessed and files can be created. Additional info: - The issue also occurs when performing a live install when the new user is only created after booting up the new system. The component is therefore likely a different one. - The issue also applies to current Fedora 31. - The issue does not apply to a Debian-based live system used for comparison. - The access is possible after adding the standard user to group vboxsf which actually exists.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
There are two issues here. First, it seems that the group does not exist, unless the virtualbox-guest-additions package is installed. Then the question is, how would the package be installed? To be clear, anaconda can sort of decide to install the package. It checks for virtualization technologies using systemd-detect-virt and install packages in the group that is named as "platform-"+(what the call detected). So the rthing to do here woudl be to find out what is reported under virtualbox, then add a group that contains the packages. (Technically that would be for relengs/release, not anaconda) Second, I'm not sure if we can just add users to groups by default. I asked on the fedora-devel mailing list about that. Theoretically we could just try to add user to the group and let it fail silently...