Windows executable on unwritable removable media cannot execute with Wine due to lack of executable bit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Triaged
|
High
|
Unassigned | ||
udisks |
New
|
Undecided
|
Unassigned | ||
Baltix |
New
|
Undecided
|
Unassigned | ||
mime-support (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Won't Fix
|
High
|
Unassigned | ||
Maverick |
Invalid
|
High
|
Unassigned | ||
udisks (Ubuntu) |
Incomplete
|
High
|
Unassigned | ||
Lucid |
Won't Fix
|
High
|
Unassigned | ||
Maverick |
Invalid
|
High
|
Unassigned |
Bug Description
I would like to install Far Cry from the DVD on Ubuntu Lucid but I wasn't able to do so because the installation executable was lacking the executable bit. I verified in fstab and there was the exec option on the cdrom line. Furthermore I was able to install Counter Strike from the CDROM (is there a difference between how DVD and CDROM are managed?). I had to umount the DVD and mount it again in an other folder, /usr/cd (/mnt/cd didn't work) to get the install executable work.
== Regression details ==
Discovered in version: lucid
Last known good version: karmic, which had no cautious-launcher
== Workaround ==
Install Wine from the Wine Team PPA, which disables the use of cautious-launcher
summary: |
- Windows executable on a DVD don't want to execute withe Wine due to lack + Windows executable on a DVD don't want to execute with Wine due to lack of executable bit |
description: | updated |
affects: | gvfs (Ubuntu) → udisks (Ubuntu) |
summary: |
- Windows executable on a DVD don't want to execute with Wine due to lack - of executable bit + Windows executable on unwritable removable media cannot execute with + Wine due to lack of executable bit |
Changed in mime-support (Ubuntu Lucid): | |
status: | New → Confirmed |
Changed in mime-support (Ubuntu Maverick): | |
status: | New → Confirmed |
Changed in udisks (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in udisks (Ubuntu Maverick): | |
status: | New → Triaged |
Changed in udisks (Ubuntu Lucid): | |
importance: | Undecided → High |
Changed in udisks (Ubuntu Maverick): | |
importance: | Undecided → High |
Changed in mime-support (Ubuntu Lucid): | |
importance: | Undecided → High |
Changed in mime-support (Ubuntu Maverick): | |
importance: | Undecided → High |
tags: |
added: lucid regression-release removed: regression-potential |
description: | updated |
description: | updated |
description: | updated |
Changed in hundredpapercuts: | |
status: | New → Confirmed |
Changed in hundredpapercuts: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
As you only see this with some disk my guess is that this may be due to a faulty Rock Ridge extension on the disk. After inserting the disk check the output of 'sudo dmesg'.
What you are looking for is lines like "ISO 9660 Extensions: RRIP_1991A" or "ISO 9660 Extensions: IEEE_P1282". If you see any of those lines the disk has a Rock Ridge extension that contain access information for the files on the disk. You can try to mount the disk with the "norock" option to disable the extension and use default access rights.