Bug 284638

Summary:	Burned disk is not valid
Product:	[Applications] k3b	Reporter:	linuxboy <linuxboy>
Component:	Burning/Hardware	Assignee:	k3b developers <k3b>
Status:	REPORTED ---
Severity:	major	CC:	linuxboy, stasnel, trueg
Priority:	NOR
Version:	2.0.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description linuxboy 2011-10-21 19:09:31 UTC

Version:           2.0.2 (using KDE 4.7.1) 
OS:                Linux

Kubuntu 11.10, kernel 3.0.0-12generic, KDE 4.7.1, K3B 2.02

After I've burn a disk from selecting some AVI files and use menu shortcut for Data Project Creation, the burn process end successfully.

Howewer, all computers I can test (4 linux, 6 Win) refuse to load the disk burned (appears as a not recognized cdrom format). I've try to burn with:
a different cd burner
a different cd burner on another PC
some different disk

None works.

I try also to create an ISO image with K3B and then I've write the ISO on disk... and SURPRISE, the disks burned this way are perfectly readable.

Some ideas?





Reproducible: Always

Steps to Reproduce:
burn a data project on disk, then load disk in the computer

Actual Results:  
disk is not readable

Expected Results:  
disk is readable.

OS: Linux (i686) release 3.0.0-12-generic
Compiler: gcc

Comment 1 linuxboy 2011-10-30 15:36:53 UTC

Further information about the problem reported:

The problem occurs with DVD data. If you burn a DVD data by adding files to the new project, K3B creates a DVD that has a format that is not recognized. The only way to burn is to create an ISO image and then write the ISO image to DVD.

The problem also occurs if you avoid writing on the fly, enabling the option to create an image first and then burn.

Brasero seems to have the same problem (maybe it's a problem or mkisofs wodim? The kernel 3.0?)

If you insert the newly burned disc into the DVD and mount it manually from the shell, SURPRISE, files are accessible.

Comment 2 Justin Zobel 2021-03-09 06:28:24 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.