GParted does not work in GNOME on Wayland

Bug #1652282 reported by Nikita Yerenkov-Scott on 2016-12-23
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GParted
Confirmed
High
Ubuntu GNOME
High
Unassigned
gparted (Ubuntu)
High
Unassigned

Bug Description

I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 that GParted does not run when I try to run it as root. That is when I click the icon and enter my password nothing happens. I have found that when running what is run when the icon is clicked that the output in Terminal is (gparted-pkexec):

    Created symlink /run/systemd/system/-.mount → /dev/null.
    Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
    Created symlink /run/systemd/system/boot.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/tmp.mount → /dev/null.
    No protocol specified

    (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
    Removed /run/systemd/system/-.mount.
    Removed /run/systemd/system/boot-efi.mount.
    Removed /run/systemd/system/boot.mount.
    Removed /run/systemd/system/run-user-1000.mount.
    Removed /run/systemd/system/run-user-120.mount.
    Removed /run/systemd/system/tmp.mount.

So I am now unable to launch and use GParted as root which is really the only way I can run it in order to make changes.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gparted 0.25.0-1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 23 11:13:13 2016
InstallationDate: Installed on 2016-05-15 (221 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gparted
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

Changed in gparted:
importance: Unknown → Medium
status: Unknown → Confirmed
Phillip Susi (psusi) wrote :

And can you run any other Xwindows app as root? What if you try running gpartedbin directly from a root shell?

Changed in gparted (Ubuntu):
status: New → Incomplete

No, this is a security feature in Wayland, it's not meant to allow windows to run as root. This has already been established in the upstream report.

Phillip Susi (psusi) on 2017-02-07
summary: - GParted fails to run as root under Wayland
+ Wayland default policy prohibits root applications
affects: gparted (Ubuntu) → wayland (Ubuntu)
Changed in wayland (Ubuntu):
status: Incomplete → New

@Phillip, This is an intended policy and it is there for security reasons so rather than decreasing security standards, I think it would be best for GParted to simply meet them.

Jeremy Bicha (jbicha) wrote :

It was announced today that the Ubuntu Desktop Team currently intends to default to GNOME on Wayland for Ubuntu 18.04 LTS.

tags: added: wayland
removed: gnome3-ppa third-party-packages yakkety
affects: wayland (Ubuntu) → gparted (Ubuntu)
Changed in gparted (Ubuntu):
importance: Undecided → High
status: New → Triaged
summary: - Wayland default policy prohibits root applications
+ GParted does not work in GNOME on Wayland
Changed in ubuntu-gnome:
status: New → Triaged
importance: Undecided → High
Changed in gparted:
importance: Medium → High
Phillip Susi (psusi) wrote :

GParted, and plenty of other applications must be run as root, period. Wayland needs to accommodate this just as X always has.

summary: - GParted does not work in GNOME on Wayland
+ Wayland default policy prohibits root applications
affects: gparted (Ubuntu) → wayland (Ubuntu)
Jeremy Bicha (jbicha) wrote :

Phillip, please stop changing the bug title because the original bug title was correct.

GParted can be changed to make admin changes without having to run the entire UI as root.

Do you want to discuss this in #ubuntu-desktop on IRC or on the ubuntu-desktop mailing list?

@Phillip, Wayland actually does accommodate it, I have an Arch system where it works perfectly fine with running GParted as root. The reason it doesn't work on Ubuntu is not completely because of Wayland, but rather because of how Wayland has been set up by the Ubuntu GNOME team. Which is intentional for security. I don't know, but you might be able to disable this since it's probably somewhere in the configuration. I don't know, I just know that on Arch there is no issue with this with the standard Wayland.

summary: - Wayland default policy prohibits root applications
+ GParted does not work in GNOME on Wayland
no longer affects: wayland (Ubuntu)
Changed in gparted (Ubuntu):
status: New → Confirmed
Jeremy Bicha (jbicha) on 2017-04-24
Changed in gparted (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged

Same problem on Ubuntu 17.10 gnome wayland

corrado@corrado-HP-aGnome:~$ uname -a
Linux corrado-HP-aGnome 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
corrado@corrado-HP-aGnome:~$ gparted
Root privileges are required for running gparted.
corrado@corrado-HP-aGnome:~$ sudo gparted
[sudo] password for corrado:
Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.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/tmp.mount → /dev/null.
No protocol specified

(gpartedbin:2315): Gtk-WARNING **: cannot open display: :0
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot-efi.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/run-user-120.mount.
Removed /run/systemd/system/tmp.mount.
corrado@corrado-HP-aGnome:~$

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.