GNOME Bugzilla – Bug 591880
Image checksumming causes internal error
Last modified: 2009-08-27 12:52:49 UTC
Hi! I've just did some tests with the current trunk (to check the status of some older bugs) and found that the checksum plugin for images (still) doesn't work. The image is written fine, but as soon as the check should start, an internal error occurs (see attached log). Steps to reproduce: Burn an image with the image checksum plugin enabled. Regards JK
Created attachment 140829 [details] Log of internal error when burning an image
Created attachment 140868 [details] Detailed logfile of described error. I've created a detailed logfile for this bug (using -g option).
Sorry, JK, what is the difference between this bug and the next one you created #591881? Although the logs are different, the behaviour seems similar.
This bug occurs when the checksum plugin for IMAGES is enabled and you try to burn an IMAGE. Bug #591881 occurs when BOTH checksum plugins are enabled and you burn FILES (i.e. start a data project). I don't know if both bugs have the same cause but, although the error message is identical, the contexts are different so I decided to report them separately. Several similar bug reports already exist (some were reported months ago for older versions) and I tried to clear the sitation up a little bit hoping that they will finally get fixed ;) Regards JK
OK, maybe I should sum up the results of my tests thus far: What works: - enabling the file checksum plugin and burning files - enabling the image checksum plugin and burning files (fixed in #581836) What doesn't work: - enabling image checksum plugin and burning an image - enabling both plugins and burning files As you can see, it's the combination that matters ;) Regards JK
Thanks for the report JK. I tried hard but could not reproduce the bug (though I may use a newer version of brasero). I tried to consolidate the code where I think the error happens for you. If it does not fix anything I also added a new debug line that will probably help me. So could you retry with master and attach a debug log if it still does not work please? Thanks in advance.
OK, I've tested the current master, but the error still occurs! To be more exactly, I've burned the image of the current RIPLinux Version (http://www.tux.org/pub/people/kent-robotti/looplinux/rip/RIPLinuX-9.3.iso) onto a CD-RW from Verbatim. I'll attach the logfile and hope that it will help... Regards JK
Created attachment 141636 [details] Detailed logfile of the current master (cf109acb0085ad088e1128357c4eb9acc4754c19)
Sorry to bother you again, but I realized that I had just committed and not pushed my changes to the repository. I did not expect you to be so reactive. My apologies. Could you retry please?
Created attachment 141646 [details] Detailed logfile for current master (a6ce4ace76f9b31550c57bc6b9aa53b8815ccf9c) Image checksumming test: the second encounter ;) (including Philippe's debug output). It still doesn't work...
Created attachment 141656 [details] Error with image checksum plugin enabled when burning files
UPDATE : I've just noticed that the bug also occurs when burning FILES with the image checksum plugin enabled and file checksum plugin disabled! I've accidentaly attached the log before commiting this comment (see above)...
I think I managed to locate the problem. It was caused by a change in an enum definition which caused stored GConf values for checksum types to be wrong and brasero failed to handle these wrong GConf values. This is fixed in master (I managed to reproduce the bug and after the fix it worked). If it still does not work for you, please reopen the bug. Thanks for your help.
OK, seems to work! Thanks a lot! BTW, this sounds like it would have been a workaround to delete all stored brasero settings on my system, isn't it? If so, this might be a solution for people who can't upgrade (for whatever reason)... Regards JK
The fix handles values out of range and in this case defaults to MD5. That way that should fix all problems without any kind of reset.
That wasn't exactly my question. I'd like to know if there is a workaround without having to upgrade brasero. Your description of the bug sounds like one could delete some settings (maybe using gconf-editor) to make it work again. Is this true? I'm asking this because I have another machine that still runs Ubuntu 8.10 and I cannot upgrade to 9.04 currently because of issues with the binary AMD drivers. I've used to build brasero from source on that machine too, but this isn't possible anymore because of dependency issues (can't remeber which library it was, maybe gtk). If such a workaround exists, that would be helpful... Regards JK
Sorry I misunderstood you. Yes there is a workaround which is to set the correct possible values: use gconf-editor and set this key "/apps/brasero/config/checksum_image" to 2, 8, or 32 which are the only valid values and "/apps/brasero/config/checksum_image" to 4, 16 or 64. Another way is to use the plugin dialog in brasero: start brasero menu edit => plugins in the plugin dialog select image checksum plugin then click on configure button select the type of checksum you want (all are valid), click on OK/VALIDATE Do the same for the file checksum plugin. That should do the trick