Comment 5 for bug 205919

BraseroGrowisofs stdout: Executing 'genisoimage -r -J -iso-level 3 -udf -input-charset utf8 -graft-points -D -path-list /tmp/brasero_tmp_9HOO9T -exclude-list /tmp/brasero_tmp_1UMQ9T -print-size | builtin_dd of=/dev/scd0 obs=32k seek=0'
BraseroGrowisofs stderr: -allow-limited-size was not specified. There is no way do represent this file size. Aborting.

Brasero is using UDF, but genisoimage can't create an image that is only udf. The solution to this bug is in the log; Brasero needs to use the -allow-limited-size option of genisoimage when there are files greater than 2GiB. This is what K3B does.

From the man page:

-allow-limited-size
              When processing files larger than 2GiB which cannot be easily
              represented in ISO9660, add them with a shrunk visible file size
              to ISO9660 and with the correct visible file size to the UDF
              system. The result is an inconsistent filesystem and users need
              to make sure that they really use UDF rather than ISO9660 driver
              to read a such disk. Implies enabling -udf.

 -udf Include UDF filesystem support in the generated filesystem
              image. UDF support is currently in alpha status and for this
              reason, it is not possible to create UDF-only images. UDF data
              structures are currently coupled to the Joliet structures, so
              there are many pitfalls with the current implementation. There
              is no UID/GID support, there is no POSIX permission support,
              there is no support for symlinks. Note that UDF wastes the
              space from sector ~20 to sector 256 at the beginning of the disc
              in addition to the space needed for real UDF data structures.