Bug 262160

Summary:	Burn Audio CD image from cue/wav: last track is broken
Product:	[Applications] k3b	Reporter:	Niccolo Rigacci <niccolo>
Component:	Image Formats	Assignee:	k3b developers <k3b>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	trueg
Priority:	NOR
Version:	2.0.0
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Niccolo Rigacci 2011-01-05 09:56:23 UTC

Version:           2.0.0 (using KDE 4.4.5) 
OS:                Linux

I have a problem when I try to burn an audio CD image, saved as a single wav file with a cue file.

From the Tools, Burn Image menu I can select my cue file: K3b displays the track list with times for each ones but the last track, which have ??:??:?? instead. It seems that K3b cannot not compute the lenght of the entire wav, so it is unable to determine the length of the last track.

If I burn the disk, the last track comes out truncated, where the wav is complete instead.

My wav file was generated from an ape file, using ffmpeg, it is RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz

Reproducible: Always

Steps to Reproduce:
Open a wav/cue image of an audio CD from the Tools, Burn Image menu.

Actual Results:  
K3b does not display the length of the last track, it display ??:??:??

Expected Results:  
Should display the actual lemgth of the last track.

Comment 1 Andrew Crouthamel 2018-11-12 02:47:29 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

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

Comment 2 Andrew Crouthamel 2018-11-21 04:35:21 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

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

Comment 3 Justin Zobel 2023-01-10 01:52:16 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2023-01-25 05:05: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
mark the bug 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 5 Bug Janitor Service 2023-02-09 03:53:43 UTC

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!