Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gparted
gparted
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • gpartedgparted
  • Issues
  • #129

Closed
Open
Created Jan 03, 2021 by Mukundan Ragavan@nonamedotc

Unit \xe2\x97\x8f.service does not exist, proceeding anyway

From downstream (Fedora) bugreport - https://bugzilla.redhat.com/show_bug.cgi?id=1899412

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

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

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)

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.

Edited Jan 04, 2021 by Mike Fleetwood
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None