Bug 171381 - "Get Performance" Speed detection of DVD makes writer restart
Summary: "Get Performance" Speed detection of DVD makes writer restart
Status: RESOLVED UNMAINTAINED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 1.0.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-20 13:52 UTC by Vincent Petry
Modified: 2010-03-16 16:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Petry 2008-09-20 13:52:55 UTC
Version:           1.0.5 (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

First, when using my external USB DVD writer NEC DVD+-RW ND-6650A as normal DVD or CD reader works fine.
Burning CDs also works fine.

The problem is with DVDs:

When I insert a blank DVD, k3b will try to detect its possible write speeds. But when it does so, the writer restart over and over again. In k3b I can see alternatively "blank DVD-R", then "no DVD inserted", then again "blank DVD-R", then "no DVD inserted", it never stops. It means, once the write restarts, k3b will detect it again, and try to detect the speed again, which will make the writer restart, etc.

I tried doing some debugging and found out the following lines in k3bdevice.cpp in the determineSupportedWriteSpeeds() method:
      if( !getSupportedWriteSpeedsViaGP( ret, true ) )
   	   getSupportedWriteSpeedsVia2A( ret, true );

If I comment out the line with getSupportedWriteSpeedsViaGP() the problem disappears.

This is ok as a quick fix, but I think there should be another way to force either method for speed detection, for example using an option in the advanced configuration dialog.
Comment 1 markuss 2010-03-16 16:11:14 UTC
In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED.
If this bug is still valid for 2.0, please reopen it.