Version: 0.11.10 (using KDE 3.2.2, Gentoo) Compiler: gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6) OS: Linux (i686) release 2.4.26-gentoo-r6 My 1st time trying to burn a .cue/.bin file and it didn't work right off because the Windoze file had CAPS in the .cue file for the name of the .bin file. Of course the Linux file name was not in caps so I got the message "Seems not to be a usable image." because it couldn't find the context-sensitive .bin file listed in .cue. Changing the .cue file to lower-case solved the problem. Suggestions: - if the .bin file can't be found, check for non-case-sensitive and continue or offer to continue if it's found. - OR, expand this error message a bit to explain what the problem is (ie. matching .bin file listed in .cue can not be found. Check case-sensitive .cue file." would be better.
*** Bug 107359 has been marked as a duplicate of this bug. ***
*** Bug 136600 has been marked as a duplicate of this bug. ***
renamed after I was hard pressed to find it again. Changing to NEW to indicate that it is something that people ran into more frequently.
In 0.12.17 (0.12.17-1ubuntu3) k3b's selection dialog guesses the correct bin file when loading a cue file that has the bin's filename with the wrong case. No error or notification is shown to the user and md5 gets calculated normally, suggesting all is okay to start burning. However, burning still fails because k3b passes the original cue file to cdrecord/cdrdao, which causes those to not find the bin file. So part of the suggestions made by the original reporter have been implemented (http://bugs.kde.org/show_bug.cgi?id=115755), but in such a way that actually burning the image will unfortunately still fail. This was reported in Ubuntu as http://launchpad.net/bugs/75887
*** Bug 140200 has been marked as a duplicate of this bug. ***
*** Bug 142635 has been marked as a duplicate of this bug. ***