I'm not sure which of the following is relevant to a solution to the problem but here's the history.
Gparted will no longer run. In fact a number of applications that require root permissions (like Grub Customizer) won't start.
History:
I tried to burn an ISO to a DVD with K3b. I got an error message that K3b didn't have permissions to write to the DVD. So I went to the permissions settings and changed it to use burning group "burning". I got the error that there was no such group so I added myself as the group. I got the DVD to burn OK.
The I wanted to use Gparted. It opens but at the "scanning for all devices" screen it runs for a long time and nothing else happens. So I rebooted.
When my desktop opened I got the error: "No command arguements supplied! usage: KDESudo [-u <runas> command] KdeSudo will now exit.
So I changed the Startup and Shutdown to "Start with an Empty Session". The KdeSudo error message goes away but Gparted still doesn't start.
So I unchecked the "use burning group" box in K3b permissions settings and rebooted. Same problem.
Maybe some update did this and the K3b stuff is just a co-incidence?
So what did I screw up and how do I fix it?
Edit:
Both Gparted and Grub Customizer will start after a 4-5 minute run time. It's not that they don't start at all.
Gparted will no longer run. In fact a number of applications that require root permissions (like Grub Customizer) won't start.
History:
I tried to burn an ISO to a DVD with K3b. I got an error message that K3b didn't have permissions to write to the DVD. So I went to the permissions settings and changed it to use burning group "burning". I got the error that there was no such group so I added myself as the group. I got the DVD to burn OK.
The I wanted to use Gparted. It opens but at the "scanning for all devices" screen it runs for a long time and nothing else happens. So I rebooted.
When my desktop opened I got the error: "No command arguements supplied! usage: KDESudo [-u <runas> command] KdeSudo will now exit.
So I changed the Startup and Shutdown to "Start with an Empty Session". The KdeSudo error message goes away but Gparted still doesn't start.
So I unchecked the "use burning group" box in K3b permissions settings and rebooted. Same problem.
Maybe some update did this and the K3b stuff is just a co-incidence?
So what did I screw up and how do I fix it?
Edit:
Both Gparted and Grub Customizer will start after a 4-5 minute run time. It's not that they don't start at all.
Comment