Comment 6 for bug 75887

Yes that is what is causing the burning to fail, and that by itself is an error of whoever/whatever created that cue file.

But... k3b does pretend to find the bin file without any problem and calculates the md5 sum for it in the selection dialog, even when the filename specified in the cue file is wrong because of upper vs lower case.

Next, upon burning, the cdrecord tools try to use the bin filename exactly as found in the cue file (as they should!) and fail (no surprise there).

So that would be a bug. Either it should not pretend all is well when selecting the cue file (and instead warn the user); or when accepting a "wrongly named" bin file, it should make sure burning works correctly (for example by feeding a corrected copy of the cue file to cdrecord).

Anyway, current behaviour is counter-intuitive and wrong.