https://bugs.kde.org/show_bug.cgi?id=429584
Bug ID: 429584 Summary: growisofs crashes @ 99% Product: k3b Version: 19.12 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: i.proud...@oxon.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY Burning .iso file to DVD-R fails when growisofs reaches 99% independent of file size, media and hardware. Windows 10 virtual machine with same hardware OK. Writing to a DVD-RW is OK. STEPS TO REPRODUCE 1. Insert blank DVD-R into optical drive. 2. Use K3b to burn .iso file. OBSERVED RESULT K3b raises an error. Debug information shows: growisofs: 7.1 Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' /dev/sr0: engaging DVD-R DAO upon user request... /dev/sr0: reserving 1938739 blocks /dev/sr0: "Current Write Speed" is 8.2x1352KBps. .................. 4511236096/4546260992 (99.2%) @11.9x, remaining 0:03 RBU 100.0% UBU 99.6% :-[ WRITE@LBA=21df40h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument :-( write failed: Invalid argument /dev/sr0: flushing cache EXPECTED RESULT .iso file copied to DVD-R SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.1 LTS Linux 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 growisofs: 7.1 ADDITIONAL INFORMATION I have two PCs both running Kubuntu 20.04.1. Both are the result of an upgrade from Kubuntu 18.04. They have different motherboards and slightly different optical drives: Samsung SH-S223F & SH-S223B. I generated a .iso file. 4.511 GB. Burning the same .iso file to Verbatim 16x DVD-R disks fails on both machines. On the machine with the SH-S223Bdrive: Burning the same .iso file to a 4x Philips DVE-RW works. Burning the same .iso file to an Imation 8x DVD-R disks fails. This PC has VirtualBox installed and a Windows 10 virtual machine. Burning the .iso file to a Verbatim 16x DVD-R disk works. NB. I manually set the writing speed since K3b detected the wrong speed on the Verbatim disks. They are 16x and K3b initially tried to use 21x. I tried 12x and 8x with the Verbatim disks without success. I used 8x for the Imation disk. The 4.511 GB .iso file nearly fills the DVD-r (4.7 GB) so I generated a smaller .iso file: 3.927 GB. This also failed: growisofs ………………….. 3927834624/3970537472 (98.9%) @8.0x, remaining 0:04 RBU 100.0% UBU 99.7% :-[ WRITE@LBA=1d9530h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument :-( write failed: Invalid argument /dev/sr0: flushing cache The dmesg output was: [21592.617939] ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen [21592.617946] ata6.00: irq_stat 0x08000000, interface fatal error [21592.617952] ata6: SError: { UnrecovData Handshk } [21592.617969] ata6.00: cmd a0/01:00:00:00:80/00:00:00:00:00/a0 tag 31 dma 32768 out Write(10) 2a 00 00 1d 95 30 00 00 03 00res 50/00:03:00:00:80/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) [21592.617973] ata6.00: status: { DRDY } [21592.617979] ata6: hard resetting link [21592.932935] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [21592.933932] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330) [21592.933948] No Local Variables are initialized for Method [_GTF] [21592.933950] No Arguments are initialized for method [_GTF] [21592.933954] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529) [21592.934768] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330) [21592.934782] No Local Variables are initialized for Method [_GTF] [21592.934784] No Arguments are initialized for method [_GTF] [21592.934787] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529) [21592.934803] ata6.00: configured for UDMA/100 [21592.935080] ata6: EH complete -- You are receiving this mail because: You are watching all bug changes.