Description of problem: The gparted shell script uses systemctl to mask .mount units. The output of "systemctl list-units" has changed a while ago, and the script no longer understands the new output format. The .mount units are not masked, and devices could possibly be mounted while running gparted. Version-Release number of selected component (if applicable): The issue has been seen also in earlier Fedora releases. When it occurred first time I don't know. How reproducible: Always. Steps to Reproduce: 1. As root run gparted 2. 3. Actual results: [root@mybox ~]# gparted Unit \xe2\x97\x8f.service does not exist, proceeding anyway. GParted 1.1.0 configuration --enable-libparted-dmraid --enable-online-resize libparted 3.3 [root@mybox ~]# gparted Unit \xe2\x97\x8f.service does not exist, proceeding anyway. GParted 1.1.0 configuration --enable-libparted-dmraid --enable-online-resize libparted 3.3 The .mount units are not masked. Expected results: The .mount units are masked while running gparted, and unmasked when terminating gparted. Additional info: [root@mybox ~]# systemctl list-units --full --all -t mount --no-legend -.mount loaded active mounted Root Mount boot.mount loaded inactive dead /boot dev-hugepages.mount loaded active mounted Huge Pages File System dev-mqueue.mount loaded active mounted POSIX Message Queue File System home.mount loaded active mounted /home proc-sys-fs-binfmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System run-user-1000-gvfs.mount loaded active mounted /run/user/1000/gvfs run-user-1000.mount loaded active mounted /run/user/1000 sys-fs-fuse-connections.mount loaded inactive dead FUSE Control File System sys-kernel-config.mount loaded active mounted Kernel Configuration File System sys-kernel-debug.mount loaded active mounted Kernel Debug File System sys-kernel-tracing.mount loaded active mounted Kernel Trace File System ● sysroot.mount not-found inactive dead sysroot.mount tmp.mount loaded active mounted Temporary Directory (/tmp) var-lib-machines.mount loaded inactive dead Virtual Machine and Container Storage (Compatibility) [root@mybox ~]# Add the "--plain" keyword and you get a listing the gparted script understands. [root@mybox ~]# systemctl list-units --plain --full --all -t mount --no-legend -.mount loaded active mounted Root Mount boot.mount loaded inactive dead /boot dev-hugepages.mount loaded active mounted Huge Pages File System dev-mqueue.mount loaded active mounted POSIX Message Queue File System home.mount loaded active mounted /home proc-sys-fs-binfmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System run-user-1000-gvfs.mount loaded active mounted /run/user/1000/gvfs run-user-1000.mount loaded active mounted /run/user/1000 sys-fs-fuse-connections.mount loaded inactive dead FUSE Control File System sys-kernel-config.mount loaded active mounted Kernel Configuration File System sys-kernel-debug.mount loaded active mounted Kernel Debug File System sys-kernel-tracing.mount loaded active mounted Kernel Trace File System sysroot.mount not-found inactive dead sysroot.mount tmp.mount loaded active mounted Temporary Directory (/tmp) var-lib-machines.mount loaded inactive dead Virtual Machine and Container Storage (Compatibility) [root@mybox ~]# I don't know when systemctl got the "--plain" keyword, but it does work in Fedora33.
Would you be able to file this upstream or do you want me to?
(In reply to Mukundan Ragavan from comment #1) > Would you be able to file this upstream or do you want me to? I would appreciate if you file it upstream.
Filed upstream
FEDORA-EPEL-2021-04a00fb568 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-04a00fb568
FEDORA-2021-19376caf4d has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-19376caf4d
FEDORA-2021-6a6a6ca0ba has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6a6a6ca0ba
FEDORA-EPEL-2021-04a00fb568 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-2021-04a00fb568 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-19376caf4d has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-19376caf4d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-19376caf4d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-6a6a6ca0ba has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-6a6a6ca0ba` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6a6a6ca0ba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-19376caf4d has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-6a6a6ca0ba has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2021-04a00fb568 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.