gparted: Unit boot.mount does not exist, proceeding anyway.

English Install/Boot/Login
1 
# gparted
Unit boot.mount does not exist, proceeding anyway.
Unit sysroot.mount does not exist, proceeding anyway.
Unit tmp.mount does not exist, proceeding anyway.
Unit var-lib.mount does not exist, proceeding anyway.
Unit var.mount does not exist, proceeding anyway.
Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot.mount → /dev/null.
Created symlink /run/systemd/system/home-u.mount → /dev/null.
Created symlink /run/systemd/system/mnt-sda12.mount → /dev/null.
Created symlink /run/systemd/system/mnt-sda14.mount → /dev/null.
Created symlink /run/systemd/system/mnt-u.mount → /dev/null.
Created symlink /run/systemd/system/proc-fs-nfsd.mount → /dev/null.
Created symlink /run/systemd/system/ramdisk.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/sysroot.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
Created symlink /run/systemd/system/var-lib-machines.mount → /dev/null.
Created symlink /run/systemd/system/var-lib-nfs-rpc_pipefs.mount → /dev/null.
Created symlink /run/systemd/system/var-lib.mount → /dev/null.
Created symlink /run/systemd/system/var-lock.mount → /dev/null.
Created symlink /run/systemd/system/var-run.mount → /dev/null.
Created symlink /run/systemd/system/var.mount → /dev/null.
No protocol specified
======================
libparted : 3.2
======================
No protocol specified
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot.mount.
Removed /run/systemd/system/home-u.mount.
Removed /run/systemd/system/mnt-sda12.mount.
Removed /run/systemd/system/mnt-sda14.mount.
Removed /run/systemd/system/mnt-u.mount.
Removed /run/systemd/system/proc-fs-nfsd.mount.
Removed /run/systemd/system/ramdisk.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/sysroot.mount.
Removed /run/systemd/system/tmp.mount.
Removed /run/systemd/system/var-lib-machines.mount.
Removed /run/systemd/system/var-lib-nfs-rpc_pipefs.mount.
Removed /run/systemd/system/var-lib.mount.
Removed /run/systemd/system/var-lock.mount.
Removed /run/systemd/system/var-run.mount.
Removed /run/systemd/system/var.mount.

Is it safe to use gparted ?

2

Hi
That looks like you switched to root user via su rather than su - so have retained your user environment…

3

Yes, it is probably safe.

I did just test in a virtual machine, and I got something similar.

It looks as if “gparted” wants to make sure that mounts by “systemd” don’t interfere. So it makes temporary changes. And then, when finished, it undoes those temporary changes.

Keep in mind that “/run” is a temporary directory (mounted “tmpfs”), so it goes away when you shutdown or reboot, and a clean “/run” is created for the next boot.

4

I’ve tried

su -

but it didn’t help.

5

Well, thank you.

Using another init system probably is not possible.