Bug 294212

Summary: Burning multisession disks on DVD-R fails ( but DVD+R works )
Product: [Applications] k3b Reporter: nnonny
Component: Data ProjectAssignee: k3b developers <k3b>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nnonny, trueg
Priority: NOR    
Version: 2.0.1   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: DVD-R discdata after k3b multisession burning

Description nnonny 2012-02-16 08:55:38 UTC
Created attachment 68845 [details]
DVD-R discdata after k3b multisession burning

Version:           2.0.1
OS:                Linux


On   DVD-R disks,  multisession burning fails.  disk becomes unreadable after second session is burnt with the 'Continue multisession' option    ( single session works ) 
But  DVD+R disks, k3b works perfectly,  multiple sessions can be added and the disk stays readable.

for DVD-R disks,  k3b  seems to be using wodim for multisession burning, but for DVD+R disks, it seems to be using growisofs.   is there a way to force k3b to use growisofs for DVD-R disks also ?

on DVD-R disks the track seems to remain unfixed after the first session.  have tried ' wodim - fix ' but mediainfo still reports the track as incomplete.

ps: using Verbatim dvds


Reproducible: Always

Steps to Reproduce:

have only tried to reproduce it 2-3 times since the discs become coasters.
1. Burn DVD-R in k3b in multisession mode.
2. check disk with  ' dvd+rw -mediainfo /dev/dvd
3. Burn a second session with  Continue multisession  option


Actual Results:  
4. disk becomes unreadable

Expected Results:  

5. allow mutiple sessions to be added readably

OS: Linux (i686) release 2.6.32-5-686
Compiler: cc
Comment 1 nnonny 2012-02-20 04:37:57 UTC
i submitted this bug..

i have since tried using growisofs from the commandline to write multisession DVD-R  discs.   these attempts have been successful.   the commands used were of the form

growisofs -Z /dev/dvd  -speed=8 -v -v -V Dvdtitle  -R -J  /filelocation

for the first session and for subsequent sessions the following,

growisofs -M /dev/dvd  -speed=8 -v -v -V Dvdtitle  -R -J  /filelocation

The output of  " dvd+rw-mediainfo  /dev/dvd "  after the first session is the following (compare with the  output after the  first session for the k3b-wodim burn, which i attached in the initial submission of the bug...    growisofs seems to complete the session while wodim does not)

root@debian# dvd+rw-mediainfo /dev/dvd
INQUIRY:                [HL-DT-ST][DVD-RAM GH22NP20][2.00]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         11h, DVD-R Sequential
 Current Write Speed:   4.0x1385=5540KB/s
 Write Speed #0:        16.0x1385=22160KB/s
 Write Speed #1:        12.0x1385=16620KB/s
 Write Speed #2:        8.0x1385=11080KB/s
 Write Speed #3:        4.0x1385=5540KB/s
 Speed Descriptor#0:    00/790463 R@16.0x1385=22160KB/s W@16.0x1385=22160KB/s
 Speed Descriptor#1:    00/790463 R@16.0x1385=22160KB/s W@12.0x1385=16620KB/s
 Speed Descriptor#2:    00/790463 R@16.0x1385=22160KB/s W@8.0x1385=11080KB/s
 Speed Descriptor#3:    00/790463 R@16.0x1385=22160KB/s W@4.0x1385=5540KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    2298496*2KB=4707319808
READ DVD STRUCTURE[#0h]:
 Media Book Type:       25h, DVD-R book [revision 5]
 Last border-out at:    4290775037*2KB=8787507275776
READ DISC INFORMATION:
 Disc status:           appendable
 Number of Sessions:    2
 State of Last Session: empty
 "Next" Track:          2
 Number of Tracks:      2
READ TRACK INFORMATION[#1]:
 Track State:           complete incremental
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Track Size:            790464*2KB
 Last Recorded Address: 790463*2KB
READ TRACK INFORMATION[#2]:
 Track State:           invisible incremental
 Track Start Address:   828368*2KB
 Next Writable Address: 828368*2KB
 Free Blocks:           1469520*2KB
 Track Size:            1469520*2KB
FABRICATED TOC:
 Track#1  :             17@0
 Track#AA :             17@790464
 Multi-session Info:    #1@0
READ CAPACITY:          790464*2048=16188702
Comment 2 nnonny 2012-04-29 10:01:35 UTC
similar bug reported here ?
https://bugs.kde.org/show_bug.cgi?id=242075
Comment 3 Andrew Crouthamel 2018-11-12 02:57:08 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 4 Andrew Crouthamel 2018-11-21 04:27:04 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 5 Justin Zobel 2023-01-04 07:05:41 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 6 Bug Janitor Service 2023-01-19 05:13:12 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 7 Bug Janitor Service 2023-02-03 05:02:58 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!