Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: xrdp maintainer here. xrdp is missing a runtime dependency on the fuse3 package which contains the fusermount3 executable. Version-Release number of selected component (if applicable): 0.10.2-9 How reproducible: Very Steps to Reproduce: Either:- 1. Install a desktop which does not pull in fuse3 2. Install xrdp 3. Connect to xrdp as user 'testuser' with a remote drive enabled. Or 1. Install xrdp 2. dnf remove fuse3. xrdp will not be removed, but other packages will be. 3. Connect to xrdp as user 'testuser' with a remote drive enabled. Actual results: 1. Remote drive does not appear under ~/thinclient_drives 2. chansrv log contains lines like the following:- [2025-03-05T14:57:01.439+0000] [ERROR] FUSE mount on /home/testuser/thinclient_drives failed. If /home/testuser/thinclient_drives is already mounted, you must first unmount it 3. journalctl reveals the additional lines:- fuse: failed to exec fusermount3: No such file or directory Expected results: 1. Remote drive appears as expected. 2. None of the errors above are logged. Additional info: - Link to original xrdp issue and triage on Github provided below. - fusermount3 is not called directly from the 'chansrv' xrdp executable, but is made from an upcall in libfuse itself. Call trace is as follows:- 1. chansrv calls fuse_session_mount() 2. fuse_session_mount() calls fuse_kern_mount() 3. fuse_kern_mount() calls fuse_mount_sys(). This returns -2 as the user has no privilege to effect the mount directly. 4. fuse_kern_mount() calls fuse_mount_fusermount() as a fallback. 5. fuse_mount_fusermount() calls fusermount_posix_spawn() 6. fusermount_posix_spawn() attempts to run the missing fusermount3 libfuse is packaged in fuse3-libs. This is pulled in automatically by the standard RPM dependency processing. However fuse3-libs has no dependency to pull in the fusermount3 executable, even though a call to fuse_session_mount() can result in it being required. I don't know what the correct solution would be. Adding a simple requires: to xrdp.spec would fix this, but there may be other packages affected by the current packaging of libfuse. The OP who raised the xrdp issue has noted that the fallback to fusermount3 can be avoided by setting CAP_SYS_ADMIN on the chansrv executable. This does not appear to be a sensible solution to this problem.
FEDORA-2025-39d4812d48 (xrdp-0.10.2-11.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-39d4812d48
FEDORA-EPEL-2025-7b7f252122 (xrdp-0.10.2-11.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7b7f252122
FEDORA-EPEL-2025-dcd555e576 (xrdp-0.10.2-11.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-dcd555e576
FEDORA-2025-caeeaf2274 (xrdp-0.10.2-11.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-caeeaf2274
FEDORA-EPEL-2025-7b7f252122 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7b7f252122 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-caeeaf2274 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-caeeaf2274` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-caeeaf2274 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-dcd555e576 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-dcd555e576 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ed16e02f32 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ed16e02f32` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed16e02f32 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-39d4812d48 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-39d4812d48` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-39d4812d48 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-39d4812d48 (xrdp-0.10.2-11.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-caeeaf2274 (xrdp-0.10.2-11.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-ed16e02f32 (xrdp-0.10.2-11.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-7b7f252122 (xrdp-0.10.2-11.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-dcd555e576 (xrdp-0.10.2-11.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.