[Bug 114758] Re: k3b error when writing and verifying DVDs using slimline drive

[ffer]

This takes place after the disk has burned 100% and k3b ejected it and means
to close the drive to 'refresh' it.  But it gets stuck and sits there using
100% cpu.  Disabling "eject disk after burn" fixes the problem because it
doesn't eject the disk and sit using 100% CPU.  The progress is at 50%
because that portion is for burning the disk and it completed, the next 50%
is the verification process.  I still have this problem, I will check again
today to verify everything.

Thank you for looking at this bug!


On Tue, May 19, 2009 at 3:00 AM, Teej <xteejyx at googlemail.com> wrote:

> I do not believe so. The disc manufacturers ratings are there for a
> reason. I assume there is a good reason that K3B was holding you back,
> i.e. to save possible data corruption with burn speed vs disc rating. I
> have had a look around the KDE bug tracker, and it appears similar
> problems have been reported before, and marked Invalid there
> https://bugs.kde.org/show_bug.cgi?id=90724 , as cdrecord is designed
> that way, and they have no intention of changing it for now, therefore I
> believe this should be Invalidated, as I do not believe this is a bug,
> but how K3B was designed to work. You can still put this forward as an
> idea to improve Ubuntu by going to http://brainstorm.ubuntu.com/ and
> submitting your idea for consideration to the community. Thank you for
> reporting this bug, and feel free to report any more you may find! :)
>
> ** Bug watch added: KDE Bug Tracking System #90724
>   http://bugs.kde.org/show_bug.cgi?id=90724
>
> ** Changed in: k3b (Ubuntu)
>       Status: Incomplete => Invalid
>
> --
> k3b error when writing and verifying DVDs using slimline drive
> https://bugs.launchpad.net/bugs/114758
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
k3b error when writing and verifying DVDs using slimline drive
https://bugs.launchpad.net/bugs/114758
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.