Bug 256111 - Reports successful burn of image for dual layer DVD but disk is unreadable.
Summary: Reports successful burn of image for dual layer DVD but disk is unreadable.
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Copying (show other bugs)
Version: 2.0.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-05 03:25 UTC by Phil
Modified: 2023-02-03 05:02 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phil 2010-11-05 03:25:13 UTC
Version:           2.0.1 (using KDE 4.4.4) 
OS:                Linux

I have two burners a LG GH22NP20 and a liteon iHAP122 9
both successfully burn dual layer dvds on openSUSE 10.3
K3B version 1.0.5  KDE version 3.5.7
 
On openSUSE 11.3  K3B version 2.0.0 & 2.0.1  KDE 4.4.4 r3
K3B reports a successful burn for dual layer dvds for the LG burner however
the disks are unreadable. (I suspect it is over writing the first layer)

also K3B slows down to a crawl when using the liteon burner when it reaches approx 52 percent of the burn, presumably at the layer change over.

No problems with either burner for single layer dvds


Reproducible: Always

Steps to Reproduce:
Happens consistently when burning an iso file large enough to require a dual layer dvd and is consistent for a variety of dual layer dvd brands
Now have about 12 shiny coasters from testing this. 



OS: Linux (x86_64) release 2.6.34.7-0.5-desktop
Compiler: gcc
Comment 1 Andrew Crouthamel 2018-11-12 02:54:37 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:28:42 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-04 07:05:28 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-19 05:12:56 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-03 05:02:45 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!