Bug 263625 - K3b crashes writing cue in single FLAC mode
Summary: K3b crashes writing cue in single FLAC mode
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Audio Project (show other bugs)
Version: 2.0.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-01-19 10:27 UTC by Christopher Yeleighton
Modified: 2018-10-27 02:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2011-01-19 10:27:51 UTC 
Version:           2.0.0 (using KDE 4.4.4) 
OS:                Linux

K3b crashes writing cue in single FLAC mode, stack trace unavailable.

Reproducible: Always

Steps to Reproduce:
  1. Get audio CD with virtual track markers (continuous play, no gaps).
  2. 
Tell K3d to rip the first two tracks to single FLAC file with paranoia=3 and cue

Actual Results:  
  2. 
K3d crashes somewhere after writing audio data (segmentation fault).  Stack trace is unavailable. flac exists, cue does not.

Expected Results:  
  2.
K3b should write the cue file and finish.


Workaround: Does not happen in WAV mode
Comment 1 Johannes Obermayr 2014-09-17 21:54:51 UTC 
Is that still valid on current packages from Packman repository?
Comment 2 Andrew Crouthamel 2018-09-25 03:50: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 3 Andrew Crouthamel 2018-10-27 02:08:37 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!