Do not use --enable-xhost-root

Bug #1737248 reported by Jeremy Bicha on 2017-12-08
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gparted (Debian)
New
Unknown
gparted (Ubuntu)
Undecided
Unassigned

Bug Description

I'm filing this as a tracking bug.

Ubuntu does not wish to use the --enable-xhost-root option in gparted. This
ugly workaround was introduced upstream in
https://git.gnome.org/browse/gparted/commit/?id=f38ccd02

However, it only works because gparted still uses gtk2 and will stop working once it's ported to gtk3. That is because gtk3 apps benefit from native Wayland support, but gtk2 apps run under XWayland. xhost
won't help when X isn't used.

We do not want to encourage other apps to use this workaround. We do want to encourage gtk2 apps to switch to gtk3.

The proper fix is for gparted to run the GUI with normal permissions and use non-graphical PolicyKit helpers to perform the specific actions that need elevated permissions

Workarounds for affected users
==============================
1. Log out. Click your name on the login screen then click the gear button and select Ubuntu on Xorg (or GNOME on Xorg). Enter your password.

2. Or, try using the GNOME Disks app (gnome-disk-utility) which runs fine with Wayland and is already installed by default.

Curtis Gedak (gedakc) wrote :

I respectfully disagree with this decision.

Fortunately there are other distros that permit their users to seamlessly use GParted with GNOME and Wayland [1].

[1]: Fedora GParted Package
https://koji.fedoraproject.org/koji/buildinfo?buildID=988102

Changed in gparted (Debian):
status: Unknown → New
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gparted - 0.30.0-3ubuntu1

---------------
gparted (0.30.0-3ubuntu1) bionic; urgency=medium

  * Sync with Debian (LP: #1709140, LP: #1735833)
  * Don't set --enable-xhost-root (LP: #1737248) (Closes: #883812)
  * Build-Depend on policykit-1 to install the PolicyKit policy
  * Install primary binary to /usr/sbin/; it didn't seem to run
    correctly in /usr/bin/

gparted (0.30.0-3) unstable; urgency=medium

  * Disable make check again.

gparted (0.30.0-2) unstable; urgency=medium

  * Merge the following changes from Ubuntu:
  * Switch to simple dh7 style rules
  * Enable all hardening flags
  * Bump debhelper compat to 10
  * Update debian/watch to watch for .gz or .xz tarballs too
  * Drop obsolete dirs, menu and .xpm
  * Drop gparted.postinst which fixed a mistake from Debian Lenny

gparted (0.30.0-1) unstable; urgency=medium

  * New upstream release (Closes: #857015, #432141)
  * Drop 01_fix-desktop.patch
  * Drop 02_use-pkexec.patch: upstream now uses pkexec (Closes: #658314)
  * Disable make check as it fails in chroot

 -- Jeremy Bicha <email address hidden> Fri, 08 Dec 2017 15:41:02 -0500

Changed in gparted (Ubuntu):
status: Fix Committed → Fix Released
Thomas Beyer (tb-beyercenter) wrote :

well, this is bad decision because it simply broke gparted!
workaround (switching to gnomedisk...hahaha) it not helping or fixing any problem with gparted and wayland.

Still having this problem:
corrado@corrado-p13-dd-1107-x:~$ apt policy gparted
gparted:
  Installed: 0.32.0-1ubuntu1
  Candidate: 0.32.0-1ubuntu1
  Version table:
 *** 0.32.0-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-p13-dd-1107-x:~$

Problem still persists in Ubuntu 18.10.

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.