Bug 314519 - K3b exits with errno 5 when burning a 4.4 GB iso image file on a 4.7 GB DVD+RW
Summary: K3b exits with errno 5 when burning a 4.4 GB iso image file on a 4.7 GB DVD+RW
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Image Formats (show other bugs)
Version: 2.0.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-06 14:25 UTC by patrick.schutyser
Modified: 2023-02-02 22:06 UTC (History)
3 users (show)

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


Attachments
attachment-29392-0.html (2.15 KB, text/html)
2023-02-02 19:51 UTC, patrick.schutyser
Details

Note You need to log in before you can comment on or make changes to this bug.
Description patrick.schutyser 2013-02-06 14:25:27 UTC
Devices
-----------------------
LITE-ON DVDRW LH-20A1P KL0G (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]

System
-----------------------
K3b Version: 1.91.0
KDE Version: 4.4.5 (KDE 4.4.5)
QT Version:  4.6.2
Kernel:      2.6.32-45-generic

Used versions
-----------------------
cdrecord: 1.1.10

cdrecord
-----------------------
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.10
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 1 = CD-ROM
Driveropts: 'burnfree'
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'LITE-ON '
Identification : 'DVDRW LH-20A1P  '
Revision       : 'KL0G'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x001A (DVD+RW)
Profile: 0x002B (DVD+R/DL) 
Profile: 0x001B (DVD+R) 
Profile: 0x001A (DVD+RW) (current)
Profile: 0x0016 (DVD-R/DL layer jump recording) 
Profile: 0x0015 (DVD-R/DL sequential recording) 
Profile: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x0012 (DVD-RAM) 
Profile: 0x0011 (DVD-R sequential recording) 
Profile: 0x0010 (DVD-ROM) 
Profile: 0x000A (CD-RW) 
Profile: 0x0009 (CD-R) 
Profile: 0x0008 (CD-ROM) 
Profile: 0x0002 (Removable disk) 
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags   : SWABAUDIO BURNFREE 
Supported modes: PACKET SAO
Drive buf size : 1068032 = 1043 KB
FIFO size      : 12582912 = 12288 KB
/usr/bin/wodim: WARNING: Could not manage to find medium size, and more than 90 mins of data.
Speed set to 5540 KB/s
Track 01: data  4467 MB        
Total size:     5130 MB (508:17.66) = 2287325 sectors
Lout start:     5130 MB (508:19/50) = 2287325 sectors
Current Secsize: 2048
HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction.
Starting to write CD/DVD at speed   4.0 in real SAO mode for single session.
Last chance to quit, starting real write in    2 seconds.
   1 seconds.
   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Sending CUE sheet...
Starting new track at sector: 0
Track 02:    0 of 4467 MB written.
Track 02:    1 of 4467 MB written (fifo 100%) [buf  98%]   0.3x.
Track 02:    2 of 4467 MB written (fifo  99%) [buf  99%]   4.0x.
Track 02:    3 of 4467 MB written (fifo  99%) [buf  98%]   4.1x.
Track 02:    4 of 4467 MB written (fifo 100%) [buf  99%]   4.0x.
Track 02:    5 of 4467 MB written (fifo  99%) [buf  99%]   4.1x.
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB:  2A 00 00 00 0B DE 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 0C 00 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 2.009s timeout 200s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 6221824 bytes
Writing  time:   19.987s
Average write speed 111.0x.
Min drive buffer fill was 98%
Fixating...
Fixating time:    0.003s
/usr/bin/wodim: fifo had 290 puts and 99 gets.
/usr/bin/wodim: fifo was 0 times empty and 48 times full, min fill was 97%.

cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=4 -sao driveropts=burnfree -data -tsize=2287325s -


Reproducible: Always

Steps to Reproduce:
1. The source image file is CentOS-5.9-x86_64-bin-DVD-1of2.iso
2. Start K3B
3. Select "More options" > burn image
4. Select image to burn
5. Settings : Verify written data
All other settings default
I tried different speeds, but this didn't solve the problem
Actual Results:  
see the logfile reproduced in "Details above

Expected Results:  
It should have created a bootable DVD.

The same error occurs when writing an iso file of 718.3 MB.
Comment 1 joerg.schilling 2013-12-19 14:53:47 UTC
You are not using recent original software but something with intentional bugs
distributed by people from Debian.

Try fo upgrade to recent original software from ftp.berlios.de/pub/cdrecord/alpha/

There is no working DVD support in "wodim"....
Comment 2 Andrew Crouthamel 2018-11-12 02:54:07 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 3 Andrew Crouthamel 2018-11-21 04:38:31 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 4 joerg.schilling 2018-11-21 11:18:59 UTC
Please however be careful: Some unfriendly Linux distros still ship the
dead fork called "cdrkit" that results in a source state from May 2004.
So you should warn your users in case that old software has been installed.

Make sure to use a PATH that finds /opt/schily/bin/mkisofs before
/usr/bin/mkisofs and inform your users that recent software is at this
location:

Bi-weekly snapshots (recommended):
http://sourceforge.net/projects/schilytools/files/

Less frequent regular release:
http://sourceforge.net/projects/cdrtools/files/alpha

So called "stable" release:
http://sourceforge.net/projects/cdrtools/files/
Comment 5 Justin Zobel 2023-01-18 02:40:55 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-02-02 05:00:43 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 patrick.schutyser 2023-02-02 19:51:03 UTC
Created attachment 155897 [details]
attachment-29392-0.html

Sir, Madam

When I reported this bug in 2013, I was using a now defunct Ubuntu version
on hardware that has died years ago. Currently I'm using Ubuntu 22.04.1
LTS, which no longer uses kde.

So iI'm afraid I can't possibly give you meaningful feedback regarding this
bug. If I'm the sole reporter of this bug, I would suggest you close it.

Best regards,

Patrick

Op do 2 feb. 2023 om 06:00 schreef Bug Janitor Service <
bugzilla_noreply@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=314519
>
> --- Comment #6 from Bug Janitor Service <bug-janitor@kde.org> ---
> 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!
>
> --
> You are receiving this mail because:
> You reported the bug.