Bug 318360 - Is not possible open .CUE files
Summary: Is not possible open .CUE files
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Audio Project (show other bugs)
Version: 2.0.2
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-04-14 20:32 UTC by Renato S. Yamane
Modified: 2018-10-27 03:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
K3B crashed by opening a cue file for burning an audio cd (9.97 KB, text/plain)
2013-12-29 18:18 UTC, Bernhard Schülke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Renato S. Yamane 2013-04-14 20:32:24 UTC
When I double-click on a .cue file, I receive an error message on K3B:

"Is not possible open the document"

No detail is available.

Reproducible: Always




I open the .cue file on KATE and it have this:
=========================================
REM GENRE Jazz
REM DATE 1999
REM DISCID 9C0EBE0C
REM COMMENT "ExactAudioCopy v0.95b3"
CATALOG 7243521810250
PERFORMER "Patricia Barber"
TITLE "Cafe Blue"
FILE "Patricia Barber - Cafe Blue\01 - What A Shame.wav" WAVE
  TRACK 01 AUDIO
    TITLE "What A Shame"
    PERFORMER "Patricia Barber"
    ISRC USPR59400001
    INDEX 01 00:00:00
=================================

On the folder "Patricia Barber" I can see FLAC files. Even editing .cue file and changing to flac instead wav, the same problem happening.
Comment 1 Bernhard Schülke 2013-12-29 18:18:19 UTC
Created attachment 84328 [details]
K3B crashed by opening a cue file for burning an audio cd

K3B crashed by opening a cue file for burning an audio cd
Comment 2 Johannes Obermayr 2014-08-31 20:59:55 UTC
Please start k3b via console:
$ kdebugdialog --on k3b
$ k3b

We need all output ...

When providing this information please set status back to "UNCONFIRMED".
Comment 3 Andrew Crouthamel 2018-09-25 03:34:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 03:49:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!