Forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=525514 Description of problem: Xfburn cannot blank disc which is mounted - it complains "Cannot access drive (it might be in use)". The problem is that in Xfce a disk is auto mounted when you insert it but there is no option to unmount it only to eject. Because of this xfburn should unmout a disk when you want to erase it. Version-Release number of selected component (if applicable): fedora-release-11.91-3 Xfce 4.6.1 xfburn-0.4.2-1.fc12.x86_64 How reproducible: 100% Steps to Reproduce: 1.run xfburn 2.insert a RW disk with some data on it 3.Blank Disc Actual results: xfburn complains "Cannot access drive" Expected results: xfburn unmount a disk and blank it. Additional info: (nor sure if this is releated) $ xfburn ** Message: Using Thunar-VFS 1.0.1 ** Message: Using HAL ** Message: Using gstreamer transcoder. ** (xfburn:4682): WARNING **: Unable to grab the drive at path '/dev/sr0' (ret=0). ** (xfburn:4682): WARNING **: Couldn't grab drive in order to update speed list. ** (xfburn:4682): WARNING **: Unable to grab the drive at path '/dev/sr0' (ret=0). ** (xfburn:4682): WARNING **: Couldn't grab drive in order to update speed list.
This should not happen. ThunarVFS & hal are used to try to unmount the disc for exactly that reason. I have no idea why this doesn't work anymore - or is hal support not compiled in?
HAL is compiled in, but in Fedora we use devicekit-disks nowadays.
I thought hal was still running alongside devicekit. Is that not true for fedora? Anyway, the output does not give me enough info to see what exactly is failing. Did the dialog about unmounting the disc pop up? I created a tarball which includes debugging messages to see where exactly in the unmounting processs the failure occurs. If you could test the tarball at http://dsp.mcbf.net/test/xfburn-0.4.3git-3cc125d.tar.bz2 that would be great (you have to configure with --enable-debug=full). If you are curious, look for "bug: " messages in the console output.
Ok, finally installed Fedora. A bit of a pain in the ass, but anyway :) I'm wondering if this bug was related to the fc12 beta. I can't reproduce it on fc12 final. Here it unmounts the disc on startup, just as I would expect. Please comment on this bug if you are somehow still experiencing this, but for now I'm closing it.
Right, it ejects on startup, but burning fails if you insert the disc after starting xfburn. Sorry if I wasn't clear enough. :(
Hmm, yeah, the description was not clear. The steps to reproduce actually are, so it's at least partially my bad. I can reproduce the problem now, it's not fedora specific. A bugfix should be out in the next couple of days, and a release should follow shortly after.
Ok, fixed in git: commit 4bf5494c29d3fa87657c99251e57bd5a999d1285 Author: David Mohr <squisher@xfce.org> Date: Thu Jan 28 21:45:35 2010 -0700 Remove accessible attribute of xfburn_device, since this can change pretty much at any time. Now check for unmount whenever we try to grab the drive. Pretty easy patch. If only I had understood the problem earlier... :-)