Hi,
under the assumption that your Brasero is configured to use libburn,
it is me who is responsible for the lower levels of drive operation.
I propose we discuss the problem on that lower level first in order
to either find a bug of libburn or to tell Brasero maintainers what
Brasero is supposed to do.
(Can it be that 2.30.3 is quite old ? Too old for BD ?)
For the inspection, get xorriso,
- either from Debian "testing"
- or as tarball from
http://www.gnu.org/software/xorriso/xorriso-1.2.4.tar.gz
To be built by
tar xzf xorriso-1.2.4.tar.gz
cd xorriso-1.2.4
./configure && make
Usable within the xorriso-1.2.4 directory without installation as
xorriso/xorriso
instead of just "xorriso" as with the Debian package.
Then let xorriso inspect the medium.
Assuming that the drive address is /dev/sr0, do:
xorriso -outdev /dev/sr0 -toc
This should report something like
Drive current: -outdev '/dev/sr0'
Drive type : vendor 'Optiarc' product 'BD RW BD-5300S' revision '1.04'
Media current: BD-R sequential recording
Media product: MEI/RA1/1 , Panasonic Corporation
Media status : is blank
Media blocks : 0 readable , 12219392 writable , 12219392 overall
Media summary: 0 sessions, 0 data blocks, 0 data, 23.3g free
If it does, then you would need to install a newer version of Brasero
for which we can find a source code repository. With some forth and back
it should be possible to find out why it does not recognize libburn's
readiness to deal with the medium.
If xorriso does not report like abve, then execute again with verbous
SCSI command log:
xorriso -report_about debug -scsi_log on -outdev /dev/sr0 -toc 2>&1 \
| tee -i /tmp/xorriso.log
The content of file /tmp/xorriso.log would be of interest.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
