GNOME Bugzilla – Bug 562740
brasero errors on inability to mount disk after burning on a laptop
Last modified: 2009-06-20 11:52:33 UTC
brasero-0.8.3 spit me an error in the end of the burn process to a DVD-R that amounted to inability to mount the drive (I think the error pop-up was about an unhandler error and the log told what's going on). Sorry for no having saved the logs, anyhow: I believe it was trying to reload the disk, so eject and load tray back, but as it's a laptop optical disk drive, there is no way it can close the bay in software, but it still is spitting an error, which is not nice for such an expected failure. Perhaps just be silent, or ask the user to close the bay herself if the drive in question is a laptop drive (I hope there's a way to figure it out if it is or not). Sorry if this has been fixed in trunk already, and sorry if I'm missing on the details. Accidentally closed the logs before figuring I should actually file a bug. If this isn't caused by the logical problem I think it is, then I can provide more detail on request, as I'll be burning quite some more in the coming week to free up some disk (600GB will take a while :)
maybe this is the same bug as reported on launchpad: https://bugs.launchpad.net/brasero/+bug/294455 there are also logs posted.
Created attachment 123906 [details] My log
I've also this bug with : * brasero 0.8.2 * Ubuntu 8.10 100% repeatable. Regards, Stephane
Thanks for the report/logs and sorry for the delay. @Mart Raudsepp: What's strange here is that you're saying that you had to reload the medium into the drive which you shouldn't have to do since 0.8.1. Since that version, brasero has the ability to checksum your medium right after it was burnt (well, some 5 seconds after) without ejecting it. Are you sure it's 0.8.3 indeed? @harobed: I'm not surprised you have this bug with 0.8.2. It was fixed in 0.8.3 or so I thought. NOTE: though it's really annoying, this bug is harmless as it's just about brasero trying to mount your medium to checksum it. So the burning operation itself has been successfully performed. The problem is I can't reproduce it with SVN trunk. Could someone try SVN trunk please and test it? Another question: What's your version of GIO please?
(In reply to comment #4) > Thanks for the report/logs and sorry for the delay. > @Mart Raudsepp: What's strange here is that you're saying that you had to > reload the medium into the drive which you shouldn't have to do since 0.8.1. > Since that version, brasero has the ability to checksum your medium right after > it was burnt (well, some 5 seconds after) without ejecting it. Are you sure > it's 0.8.3 indeed? Yes, I'm sure. Additionally I have tried to now burn with the "Eject after burn" option OFF. It doesn't eject, but it gives me a mount error still and nautilus still sees an empty media. I manually eject, reload again and then at least this one time now it was still seeing empty DVD media. I manually eject and reload again, then it sees the burn results. Additionally I'm quite unhappy about the ".checksum.md5" file that brasero seems to burn onto the media. It will look weird on Windows systems, takes unnecessary bytes and just seems unwarranted (while it could internally be used for something, I think a better solution than burning extra files to disk would be nice) > @harobed: I'm not surprised you have this bug with 0.8.2. It was fixed in 0.8.3 > or so I thought. This is definitely 0.8.3, yes. I'll check for next burning sessions that I'm up to date on libburn/cdrkit and the like. > NOTE: though it's really annoying, this bug is harmless as it's just about > brasero trying to mount your medium to checksum it. So the burning operation > itself has been successfully performed. Yes, but there is an annoying and very confusing error in the process, and it isn't showing me the new media before I manually eject and reload the tray. > The problem is I can't reproduce it with SVN trunk. Could someone try SVN trunk > please and test it? > > Another question: What's your version of GIO please? $ pkg-config --modversion gio-2.0 2.18.3
OK, I tried to fix things in 0.9.1 (to be released today). Could you test it please? (In reply to comment #5) > Yes, I'm sure. Additionally I have tried to now burn with the "Eject after > burn" option OFF. It doesn't eject, but it gives me a mount error still and > nautilus still sees an empty media. I manually eject, reload again and then at > least this one time now it was still seeing empty DVD media. I manually eject > and reload again, then it sees the burn results. > Additionally I'm quite unhappy about the ".checksum.md5" file that brasero > seems to burn onto the media. It will look weird on Windows systems, takes > unnecessary bytes and just seems unwarranted (while it could internally be used > for something, I think a better solution than burning extra files to disk would > be nice) You can disable the plugin if you want ("file checksum") and that way it won't burn any checksum file to the disc. I'm also considering leaving you the possibility to write that file on a hard drive. > Yes, but there is an annoying and very confusing error in the process, and it > isn't showing me the new media before I manually eject and reload the tray. Ejection being needed is normal. The kernel needs to update its information about the disc and that can only happen with a reloading of the medium. However hard I tried I could not find a way to force it to do that automatically.
This time I think I got it. As you mentionned and as I failed to realize, brasero was indeed mounting disc to check on disc files. I changed that behavior so that we don't need to anymore. As for the impossible to unmount it was triggered by the new "burn:///" module which mounts blank disc. As after a burning hal fails to realize that things have changed on the disc almost 70% of the time, the burn:// module keeps trying to mount (and usually succeeds before us).
I forgot I'm closing it but feel free to reopen if it's not working when you can test it (0.9.2 or higher). Thanks.
I'm having the same issue with Brasero 2.26.2 on Fedora 11. It works fine with K3B. Even if Brasero is not able to eject the CD, then it should ask me to do it manually and not cancel the whole process. In the downstream bug report (https://bugzilla.redhat.com/show_bug.cgi?id=506338) there's also some criticism about how Brasero extracts audio cds. Maybe you can also look at that.