Description of problem:
gnome-mount when fed with an iso9660 CD created on Mac for some reasons
insist on mounting it with udf filesystem type even if udf is NOT listed
in /etc/filesystems. It passess 'uid=<some_value>' option to mount but
this ends up with the following structure
A directory named by "<a_random_garbage_string>" indeed gets
"<some_value>.4294967295" ownership (4294967295 happens to be -1,
when interpreted signed, on this machine) but "<some_directory_name>"
happens to have 'rwxrwx--x" permissions and "501.501" ownership where
"501" is uid and gid from Mac of somebody who wrote that CD.
See bug #159860. All real data sit below this "<some_directory_name>"
and, unless your uid happens to be 501 too, are not accessible.
If I will mount that CD with
mount -oro,uid=<some_value> /dev/cdrom /some/mount/point
then this CD mounts with 'iso9660' filesystem type, even without
explicitly specifying that, and there are no access problems.
The real issue is that I cannot dissuade gnome-mount from using
Version-Release number of selected component (if applicable):
gnome-mount-0.4-5 and gnome-mount-0.4-7 from rawhide
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.