The Testing Area :: gaprted.uci



Perhaps HAL is all of those things and worse, but it is increasingly being required as a dependency.  If the kernel support is there (which is what I meant), the userspace stuff presumably could be an extension. I suggest this is OT and for another thread.   Robert sent me a PM telling me off the last time I got OT :=)

Back to gparted.
Quote
gparted_start.sh just calls sudo gpartedbin on the uci that I have.

There is a script /opt/gparted/sbin/gparted that looks like it implements the lock with hal-lock when running gpartedbin.

[I think] Starting gpartedbin directly doesn't get around the hal requirement, and it appears no warning that it was mandatory was included in this release version.

That would make sense - I thought that gpartedbin might get round the hal thing, but your explanation makes more sense. I guess it might be smarter to go back a few versions (and indeed the gparted cd was a few versions earlier) and recompile gparted - sigh...
Try checking out and compiling the svn sources first.

As I said above, the developers have just removed the hal requirement (or made it optional).  There must have been other problems.

But (this early) this change will probably only be in the svn sources, not the release tarball that you built the extension from.

So maybe fire up the svn uci.
I just compiled gparted-0.3.5 to see if this would get around the hal issue and realised the cause of the problem might be something else...

gparted needs to be run as root and cannot be run via set uid root - I had started gpartedbin using sudo in the gparted_start.sh wrapper, but maybe this was, ahem, too simplistic.

I see a difference in the way gparted acts when started from a root window (exec /opt/gparted/sbin/gpartedbin &) as compared to starting it via the icon/menu item. At the moment I have only my usb boot laptop with ntfs hd to test - in both cases (icon start & root window start) gparted finds the two hd partitions, but it cannot read the partitions in the case of the icon start.

Maybe somebody could try starting gparted from a root window to see if the device detection problem goes away?

In the meantime, what is the best way to run an application as root from an icon/menu item in dsl?

original here.