typo in gparted's use of hal-lock
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gparted (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gparted
When trying to delete and recreate a partition on an external USB drive using gparted (0.3.8-1ubuntu2), I noticed that it failed halfway through its operations.
From reading gparted's changelog.Debian.gz I found that gparted is using hal-lock to lock storage devices when operating on them.
When I next looked at /usr/sbin/gparted and the hal-lock man page, I noticed a typo in the use of the hal-lock command:
After changing line 31 of /usr/sbin/gparted from
hal-lock --interface org.freedeskdes
to read:
hal-lock --interface org.freedesktop
(as per the example given in hal-lock man page) and rerunning the partition delete / recreate operations in gparted, the operations now completed successfully.
A small problem remains, and I don't know if I should file a seperate bug report for this:
After exiting gparted, choosing Places / Computer from the menu sometimes shows duplicate or wrong icons in the File Manager, which seems to indicate to me that its status of which partitions are active is out of sync.
I have sometimes managed to get rid of the duplicate icons by adding a partition check to gparted's actions.
| Jonas Pedersen (jonasped) wrote | #1 |
| Jonas Pedersen (jonasped) wrote | #2 |
| Jonas Pedersen (jonasped) wrote | #3 |
| Changed in gparted: | |
| status: | New → Confirmed |
I can confirm this typo in both jaunty and intrepid. I have created debdiff for both the current version in intrepid as well the current version in jaunty. Updated packages are also available from my PPA (as soon as intrepid version finishes build).