Summary: | case insensitive parsing of of cue file (CUE image filename CAPS) | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Richard Lees <rlees> |
Component: | Image Formats | Assignee: | k3b developers <k3b> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | becheru.petru.ioan, jbrandligt, maarten, mail, ra100 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Richard Lees
2004-08-15 06:38:25 UTC
*** 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. *** |