Bug 245111

Summary: k3b becomes unresponsive displaying 60-80% completion of an Audio CD rip to flac.
Product: [Applications] k3b Reporter: Radek Novacek <rad.n>
Component: generalAssignee: Michał Małek <michalm>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kdebugzilla, trueg
Priority: NOR    
Version: 2.0.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In: 2.0.1

Description Radek Novacek 2010-07-19 10:41:22 UTC
Version:           2.0.0 (using KDE 4.4.4) 
OS:                Linux

This is forwarded bug from Fedora's bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=613249, reported by E.Patton.

k3b becomes unresponsive displaying 60-80% completion of an Audio CD rip to
flac.The rip completes successfully but the application must be terminated
using the window manager. 


Reproducible: Always

Steps to Reproduce:
1. Select Tools->Rip audio CD
2. Select Start Ripping (post auto CDDB completion of the track names)
3. Select the file type to flac
4. The filenaming and Advanced tabs are left at default settings other than
Convert " "->"_" is selected on the filenaming tab.

Actual Results:  
At around 60-80% completion displayed, the ripping panel (and application)
becomes unresponsive and its display is no longer updated and the only way to
exit the panel is to terminate the window using the window manager.

The actual rip does succeed and is 100% complete.

Expected Results:  
The rip panel and application should remain responsive and eventually offer a
close option at completion of the rip. The rip should succeed.

Whilst verifying that the issue was not related to the CDs that I was using, I
tested with an old (>15 years) known good CD. In that instance the entire
desktop locked up and I had to shut down the system via remote login (VTs were
not accessible).

I have reproduced the same issue on my eeePC using an external USB drive in
32-bit F13.

The CD drive in use is an Optiarc DVD RW AD-7200S Rev 1.05
Comment 1 Michał Małek 2010-07-26 20:13:58 UTC

*** This bug has been marked as a duplicate of bug 236466 ***