Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2184589

Summary: Root previleges required to run GParted
Product: [Fedora] Fedora Reporter: Villy Kruse <ppywlkiqletw>
Component: gpartedAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gparted-1.5.0-2.fc37 gparted-1.5.0-2.fc38 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-12 01:33:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
pop-up window none

Description Villy Kruse 2023-04-05 06:06:25 UTC
Created attachment 1955812 [details]
pop-up window

Description of problem:

When click on gparted I get a popup saying that root is required to run this.  

Version-Release number of selected component (if applicable):

gparted-1.5.0-1.fc37.x86_64

How reproducible:

Always.

In previous version gparted-1.4.0-2.fc37.x86_64 it worked as expected.

Steps to Reproduce:
1. click on gparted or run gparted from a non-root command prompt.
2.
3.

Actual results:

A pop message saying root is required.

Expected results:

gparted is started like it used to do




Additional info:

The new gparted command does know about xpkexec, probably because the build environment did not have that command installed.
--- usr/bin/gparted	2022-07-21 15:00:22.000000000 +0200 ## old version
+++ /usr/bin/gparted	2023-03-25 12:32:53.000000000 +0100 ## new version
@@ -50,7 +50,7 @@
 	#  non-root to display the graphical error about needing root
 	#  privileges.
 	#
-	if test "xpkexec --disable-internal-agent" = "x"; then
+	if test "x" = "x"; then
 		echo "Root privileges are required for running gparted."
 		$BASE_CMD
 		exit 1
@@ -75,7 +75,7 @@
 	#
 	# Run gparted as root.
 	#
-	pkexec --disable-internal-agent '/usr/bin/gparted' "$@"
+	 '/usr/bin/gparted' "$@"
 	status=$?
 
 	#

Comment 1 Fedora Update System 2023-04-05 08:01:25 UTC
FEDORA-2023-20575c0161 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-20575c0161

Comment 2 Fedora Update System 2023-04-05 08:01:29 UTC
FEDORA-2023-04662d348c has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-04662d348c

Comment 3 Fedora Update System 2023-04-06 01:47:56 UTC
FEDORA-2023-04662d348c has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-04662d348c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2023-04-06 02:51:57 UTC
FEDORA-2023-20575c0161 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-20575c0161`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-20575c0161

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-04-12 01:33:30 UTC
FEDORA-2023-20575c0161 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2023-04-15 02:06:41 UTC
FEDORA-2023-04662d348c has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.