Description of problem: Any attempt to attach a disk image results in the program crashing. Version-Release number of selected component (if applicable): gnome-disk-utility-3.4.1-1.fc17.x86_64 How reproducible: Always. Steps to Reproduce: 1. Launch palimpsest 2. Click the PLUS button at bottom left corner of Disk Drives list. 3. Browse to and select an ISO image 4. Click Attach Actual results: Program crashes Expected results: Image mounted? Additional info: Does not seem to matter if 'Set up read-only loop device' is checked. Running as regular user or with sudo does not change result. If run from console you get the following output: patrick@crudora:~$ palimpsest g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated patrick@crudora:~$ Tried a few ISO images that work fine with an old fashioned mount -o loop
Try running it like this $ G_DBUS_DEBUG=all palimpsest and include the debug output. Thanks.
Created attachment 582202 [details] Debug output Here you are. Thank you!
Oh, let me guess - you are running in SELinux enforcing mode, right? try permissive ('setenforce 0' as root). Does that fix the problem?
Created attachment 583381 [details] selinux alert browser output setenforce 0 does fix the problem. Here is the selinux alert browser output.
Thanks, reassigning to selinux-policy. Dan: there are two different cases when udisksd exchanges file descriptors with other peers (remember that these D-Bus messages, including the file descriptors, pass through the message bus daemon): 1. when attaching a disk image file - see comment 0 for how to reproduce. In this case the unprivileged user app (typically Disks) passes a file descriptor from a file he opened (could be from anywhere) 2. when creating/restoring disk images - in this case udisksd passes a file descriptor for the underlying block device (e.g. /dev/sdb or /dev/sdb1) to the unprivileged user app (typically Disks). To reproduce, simply find an unused USB stick or similar with an unused partition. Then click the gears in the under Volumes and a menu appears [1]. Click "Create Disk Image" [2] and then "Start Creating..." [1] : http://people.freedesktop.org/~david/palimpsest2-2012-03/05-palimpsest2-volume-menu.png [2] : http://people.freedesktop.org/~david/palimpsest2-2012-03/15-palimpsest2-create-disk-image.png
Fixed in selinux-policy-3.10.0-126.fc17
selinux-policy-3.10.0-128.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-128.fc17
Package selinux-policy-3.10.0-128.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-128.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-8720/selinux-policy-3.10.0-128.fc17 then log in and leave karma (feedback).
selinux-policy-3.10.0-128.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.