Hi, for the records: I managed to get my changes in burn-libburn.c into effect by copying from brasero-2.30.3/plugins/libburnia/.libs/libbrasero-libburn.so to /usr/lib/brasero-0/plugins/libbrasero-libburn.so I assume it is better to achieve this the Debian way.
At least i could verify that it is possible to change the write type from TAO to SAO by hardcoding it in brasero-2.30.3/plugins/libburnia/burn-libburn.c Re-iterated for convenience: Change all occurences of BURN_WRITE_TAO to BURN_WRITE_SAO BURN_BLOCK_MODE1 to BURN_BLOCK_SAO I advise to issue a loud message on stderr which tells you that the change is really in effect. I have added at file start: #include <stdio.h> and where i changed the parameters, i added: fprintf(stderr, "Brasero libburn-plugin: ***************** brasero_libburn_start_record : Write type is SAO\n"); resp. fprintf(stderr, "Brasero libburn-plugin: ***************** brasero_libburn_start_erase : Write type is SAO\n"); The resulting CDs can be examined by xorriso -outdev /dev/sr0 -check_media what=disc use=outdev If it is TAO, then you get two read errors at the end. If it is SAO, then you get an inappropriate warning that your image is larger than the CD track. A little bug in libburn's CD inspection code. It will be fixed by the next release. The image should be usable anyway. Images from wodim -no-pad show the same effect. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org