Comment 3 for bug 1082411

Hi,

i am glad to see that this time not the libburn plugin is
to blame. :))

Telling from the log, i would say that burning via libburn
succeeded:

> Burning from 0 to 355990
> TAO pre-track 01 : get_nwa(0)=1, d=0 , demand=729067520 , cap=736966656
> [... no visible error messages ...]
> Aync CLOSE TRACK SESSION succeeded after 4.3 seconds
> Finished successfully session
> stopped BraseroLibburn
> End of last written track address == 355990

But then program readom was started to check the readability of
the finished CD:

> readom dev=/dev/sr0 -nocorr -noerror -sectors=0-355990 -f=-
(Collected from several lines in the log.)

This program run seems not to reach the end of the medium or
at least it does not recognize that it is time to end the program.
The last message is
> BraseroReadom stderr: addr: 355840

That's 150 blocks before the end of the track.

Proposals:

- Try to disable checkreading before you burn.
  (I am not a Brasero user, but the plumber of libburn and libisofs.
   So i cannot tell how to do this disabling.)

- If you cannot disable checkreading, then kill the readom
  process rather than Brasero, when it gets stuck.
  I assume that Brasero will then finish with an error message.

- To learn more about the problem of readom, you could run

    readom dev=/dev/sr0 -nocorr -noerror -sectors=0-355990 -f=- >/dev/null

  and see what it actually reports. (>/dev/null is important to
  avoid that the whole CD content is printed to your terminal.)

Have a nice day :)

Thomas