gparted does not start - Unit -.mount does not exist, proceeding anyway.

Bug #1744372 reported by Thomas Beyer on 2018-01-19
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gparted (Ubuntu)
Undecided
Unassigned
wayland (Ubuntu)
Undecided
Unassigned

Bug Description

1. fresh ubuntu 18.04 daily: lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04

2. install gparted with Software:
gparted:
  Installiert: 0.30.0-3ubuntu1
  Installationskandidat: 0.30.0-3ubuntu1
  Versionstabelle:
 *** 0.30.0-3ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

3. launch with icon - enter password - nothing.
4.launch in terminal:
Unit -.mount does not exist, proceeding anyway.
Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
Created symlink /run/systemd/system/home.mount → /dev/null.
Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
No protocol specified

(gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot-efi.mount.
Removed /run/systemd/system/home.mount.
Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
Removed /run/systemd/system/run-snapd-ns.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/run-user-120.mount.
Removed /run/systemd/system/snap-core-3748.mount.
Removed /run/systemd/system/snap-vlc-113.mount.
Removed /run/systemd/system/tmp.mount.

How to Fix: run xhost +local: before gparted! # this only bypass the wayland restriction; meaning a security violation (not a fix !!! )

thomas@ubuntu-1804:~$ xhost +local:
non-network local connections being added to access control list
thomas@ubuntu-1804:~$ gparted
Unit -.mount does not exist, proceeding anyway.
Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
Created symlink /run/systemd/system/home.mount → /dev/null.
Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
Gtk-Message: Failed to load module "canberra-gtk-module"
======================
libparted : 3.2
======================
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot-efi.mount.
Removed /run/systemd/system/home.mount.
Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
Removed /run/systemd/system/run-snapd-ns.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/run-user-120.mount.
Removed /run/systemd/system/snap-core-3748.mount.
Removed /run/systemd/system/snap-vlc-113.mount.
Removed /run/systemd/system/tmp.mount.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gparted 0.30.0-3ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 19:45:14 2018
InstallationDate: Installed on 2018-01-18 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gparted
UpgradeStatus: No upgrade log present (probably fresh install)

Thomas Beyer (tb-beyercenter) wrote :
summary: - gparted just dont start - Unit -.mount does not exist, proceeding
- anyway.
+ gparted does not start - Unit -.mount does not exist, proceeding anyway.
Thomas Beyer (tb-beyercenter) wrote :

I added wayland becauce there is no problem with Xorg-Windowsmanager only with (default) wayland and the suggested workaround with xhost +

dino99 (9d9) on 2018-01-19
description: updated
Changed in wayland (Ubuntu):
status: New → Invalid
Curtis Gedak (gedakc) wrote :

The upstream GParted team added a work-around to version 0.30.0 to enable it to run seamlessly under Wayland.

See https://gparted.org/news.php?item=214

Unfortunately the packager for Ubuntu decided to not use the --enable-xhost-root work-around.

See https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1737248

The consequence is that GParted only runs seamlessly on X, and not on Wayland.

If you wish to use GParted from live media, then you might consider using GParted Live.

See https://gparted.org/livecd.php

Thomas Beyer (tb-beyercenter) wrote :

thank you #3

But it is more about having wayland as default and not beeing able to use gparted withing 18.04 LTS!

Curtis Gedak (gedakc) wrote :

You might try petitioning the packager who made the decision.

https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1737248

Curtis Gedak (gedakc) wrote :

I see now that you have already done that. Perhaps if enough users express their displeasure with the decision then perhaps the packager will reconsider.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gparted (Ubuntu):
status: New → Confirmed
Andrea (gresenen) wrote :

This also affects me, running on X. When I run
  gparted
I get prompted to insert the password, then the terminal says
  Unit -.mount does not exist, proceeding anyway.
and it just hangs there.

Bougron (francis-bougron) wrote :

Hello

With version 18.04.1

gparted works but two messages are displayed

a@a:~$ sudo gparted
Unit -.mount does not exist, proceeding anyway.
Gtk-Message: 10:50:03.294: Failed to load module "canberra-gtk-module"
======================
libparted : 3.2
======================

Eduardo Gutierrez (eduardo74) wrote :

I have a similar problem not using Wayland. Ubuntu 18.04.1

eduardo@MiPcLinux:~$ sudo gparted
[sudo] contraseña para eduardo:
Unit -.mount does not exist, proceeding anyway.
======================
libparted : 3.2
======================
¡No se puede hacer una partición fuera del disco!

이야기 (iyagicom) wrote :

I did not delete libgtk-x11-2.0.so.0.
I installed 19.04 a few days ago.

Unit tmp.mount does not exist, proceeding anyway.
/usr/sbin/gpartedbin: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco

patrick samples (ptrakk) wrote :

^
apt install libgtk2.0-0

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers