| Summary: | K3B creates unapendable disks in "Start Multisession" mode | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | nvivo |
| Component: | general | Assignee: | k3b developers <k3b> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | Kicer86, nnonny, perpsectiveoffice, trueg |
| Priority: | NOR | ||
| Version: | Git | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Version of apps used by k3b | ||
|
Description
nvivo
2010-06-18 15:25:47 UTC
it's same here with: $ k3b --version Qt: 4.7.3 KDE Development Platform: 4.6.3 (4.6.3) K3b: 2.0.2 dvd+rw-mediainfo says: READ DISC INFORMATION: Disc status: complete Number of Sessions: 1 State of Last Session: complete Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: complete Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size: 336806*2KB Last Recorded Address: 336805*2KB disc becomes unappendable i had a similar problem which i have reported. see https://bugs.kde.org/show_bug.cgi?id=294212 have you checked the log ? i think it may be a problem with k3b using wodim for dvd-r disks. k3b uses growisofs for dvd+r disks and that seems to work correctly. when i use growisofs on dvd-r disks from a terminal, they are appendable. have you tried dvd+r disks ? I am having the same problem, but only when burning DVDs (DVD-R type) with more than 3.8 GB of data on them. Any data that is written above the 3.8 GB limit isn't properly written, although it sometimes can be read in Windows or (in the case of AVIs) on my DVD player. The type of data is unimportant; this behaviour occurs with any data DVD.
It matters not whether I use k3b or k9copy or Brasero or Gnomebaker as the front-end, making me think the problem is with some DVD burning software, such as recent wodim and or genisoimage/growisofs packages of cdrkit. This is the same sort of problem that happened long ago, but didn't happen for me in Lucid. (I am using the same hardware I have successfully used for years).
I went back to my Oneiric installation (I didn't use Maverick or Natty much) and sure enough, the problem is there, too. The behaviour is not just unusable/unrecognisable discs, but freezing once burning reaches 3.9 GB, or an abort, or the mysterious "error 254."
It has crippled burning DVDs above 3.8 GB for me altogether. Interestingly, there is no problem at all burning DVDs with less than 3.8 GB data on them.
Reading the Ubuntu forums I see similar complaints with Brasero on Ubuntu.
Could wodim have gotten screwed up (or genisoimage?)
It is not that easy to install the original cdrtools (cdrecord and mkisofs) in (K)Ubuntu, and I can not figure out where to set k3b to use them even when I do install them.
Another possibility is a recent (Dec 2011) change to libdvdread -- maybe this isn't fixed completely?
libdvdread (4.2.0-1ubuntu3) precise; urgency=low
* Add 103-iforead-tt-srpt-pointerfix.patch: Fix read/write beyond end of
an array due to using a length value taken from the DVD, which can
exceed the allocated size, causing a segmentation fault.
(LP: #894170)
your problem may be with STARTING a new session after the 3.8 gb mark. Have you tried going up to, say, 3.5 gb and then adding a 700 mb session to get the full 4.2 gb dvd ? i think this is a separate problem from the k3b multisession writing problem for dvd-r disks.... which i think is just a software problem since multisession writing is possible on dvd-r by using growisofs from the terminal command line. On Wed, Jun 13, 2012 at 10:04 PM, Paul Perspectoff < perpsectiveoffice@yahoo.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=242075 > > Paul Perspectoff <perpsectiveoffice@yahoo.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| | > perpsectiveoffice@yahoo.com > > --- Comment #3 from Paul Perspectoff <perpsectiveoffice@yahoo.com> --- > I am having the same problem, but only when burning DVDs (DVD-R type) with > more > than 3.8 GB of data on them. Any data that is written above the 3.8 GB > limit > isn't properly written, although it sometimes can be read in Windows or > (in the > case of AVIs) on my DVD player. The type of data is unimportant; this > behaviour > occurs with any data DVD. > > It matters not whether I use k3b or k9copy or Brasero or Gnomebaker as the > front-end, making me think the problem is with some DVD burning software, > such > as recent wodim and or genisoimage/growisofs packages of cdrkit. This is > the > same sort of problem that happened long ago, but didn't happen for me in > Lucid. > (I am using the same hardware I have successfully used for years). > > I went back to my Oneiric installation (I didn't use Maverick or Natty > much) > and sure enough, the problem is there, too. The behaviour is not just > unusable/unrecognisable discs, but freezing once burning reaches 3.9 GB, > or an > abort, or the mysterious "error 254." > > It has crippled burning DVDs above 3.8 GB for me altogether. Interestingly, > there is no problem at all burning DVDs with less than 3.8 GB data on them. > > Reading the Ubuntu forums I see similar complaints with Brasero on Ubuntu. > > Could wodim have gotten screwed up (or genisoimage?) > > It is not that easy to install the original cdrtools (cdrecord and > mkisofs) in > (K)Ubuntu, and I can not figure out where to set k3b to use them even when > I do > install them. > > Another possibility is a recent (Dec 2011) change to libdvdread -- maybe > this > isn't fixed completely? > > libdvdread (4.2.0-1ubuntu3) precise; urgency=low > > * Add 103-iforead-tt-srpt-pointerfix.patch: Fix read/write beyond end of > an array due to using a length value taken from the DVD, which can > exceed the allocated size, causing a segmentation fault. > (LP: #894170) > > -- > You are receiving this mail because: > You are on the CC list for the bug. > Thank you for the reply. I will try it. On 06/18/2012 10:03 AM, nnonny@gmail.com wrote: > https://bugs.kde.org/show_bug.cgi?id=242075 > > --- Comment #4 from nnonny@gmail.com --- > your problem may be with STARTING a new session after the 3.8 gb mark. > Have you tried going up to, say, 3.5 gb and then adding a 700 mb session > to get the full 4.2 gb dvd ? > > i think this is a separate problem from the k3b multisession writing > problem for dvd-r disks.... which i think is just a software problem since > multisession writing is possible on dvd-r by using growisofs from the > terminal command line. > > > On Wed, Jun 13, 2012 at 10:04 PM, Paul Perspectoff < > perpsectiveoffice@yahoo.com> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=242075 >> >> Paul Perspectoff <perpsectiveoffice@yahoo.com> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| | >> perpsectiveoffice@yahoo.com >> >> --- Comment #3 from Paul Perspectoff <perpsectiveoffice@yahoo.com> --- >> I am having the same problem, but only when burning DVDs (DVD-R type) with >> more >> than 3.8 GB of data on them. Any data that is written above the 3.8 GB >> limit >> isn't properly written, although it sometimes can be read in Windows or >> (in the >> case of AVIs) on my DVD player. The type of data is unimportant; this >> behaviour >> occurs with any data DVD. >> >> It matters not whether I use k3b or k9copy or Brasero or Gnomebaker as the >> front-end, making me think the problem is with some DVD burning software, >> such >> as recent wodim and or genisoimage/growisofs packages of cdrkit. This is >> the >> same sort of problem that happened long ago, but didn't happen for me in >> Lucid. >> (I am using the same hardware I have successfully used for years). >> >> I went back to my Oneiric installation (I didn't use Maverick or Natty >> much) >> and sure enough, the problem is there, too. The behaviour is not just >> unusable/unrecognisable discs, but freezing once burning reaches 3.9 GB, >> or an >> abort, or the mysterious "error 254." >> >> It has crippled burning DVDs above 3.8 GB for me altogether. Interestingly, >> there is no problem at all burning DVDs with less than 3.8 GB data on them. >> >> Reading the Ubuntu forums I see similar complaints with Brasero on Ubuntu. >> >> Could wodim have gotten screwed up (or genisoimage?) >> >> It is not that easy to install the original cdrtools (cdrecord and >> mkisofs) in >> (K)Ubuntu, and I can not figure out where to set k3b to use them even when >> I do >> install them. >> >> Another possibility is a recent (Dec 2011) change to libdvdread -- maybe >> this >> isn't fixed completely? >> >> libdvdread (4.2.0-1ubuntu3) precise; urgency=low >> >> * Add 103-iforead-tt-srpt-pointerfix.patch: Fix read/write beyond end of >> an array due to using a length value taken from the DVD, which can >> exceed the allocated size, causing a segmentation fault. >> (LP: #894170) >> >> -- >> You are receiving this mail because: >> You are on the CC list for the bug. >> > 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! 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! 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! 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! 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! |