[Bug 1652282] Re: GParted does not work in GNOME on Wayland

Nikita Yerenkov-Scott 1652282 at bugs.launchpad.net
Sat Nov 4 09:07:33 UTC 2017


So, basically, Wayland doesn't allow something really insecure where the
whole GUI and everything has root privileges, so it doesn't allow
insecure applications to gain root access, however a program can be
easily adapted (depending on how it's written) in order to be secure and
then you will be able to run it as normal under Wayland. For instance
etherape recently got adapted and you just have to now run it like so
"sudo etherape -Z username" and then it runs in a way Wayland finds
secure and thus it runs as normal as a GUI program but it just runs the
GUI as the normal specified user and only the necessary components as
root.

Anyway, has GParted upstream released a fix for this? Programs just have
to match the new security standards in order to run. That's all, they
will have to change and then your experience will be fine again. But I
don't think you're going to be able to lessen the Wayland standards,
instead take this up with the other developers so that they make their
programs meet those standards.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gparted in Ubuntu.
https://bugs.launchpad.net/bugs/1652282

Title:
  GParted does not work in GNOME on Wayland

Status in gdm:
  Unknown
Status in GParted:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in wayland:
  New
Status in gparted package in Ubuntu:
  Confirmed

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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1652282/+subscriptions



More information about the foundations-bugs mailing list