Hi,
i understand from the category "brasero package" that you inspect the drive
by Brasero.
Which burn backend is it using (cdrecord, wodim, libburn ) ?
What kind of medium did you try (CD-R, DVD+R, DVD-R, DVD+RW, BD-R, ...) ?
Which task of Brasero do you want to perform (Audio project, Data proj
I forgot to ask for putting in the desired medium before performing
xorriso -outdev /dev/sr0 -toc
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/1896804
Title:
CD/DVD drive dete
Hi,
> Sense Key 6 "Drive event", ASC 28 ASCQ 81.
This SCSI error reply is not listed in SCSI specs SPC or MMC or in the
summary of T10 committee
https://www.t10.org/lists/asc-num.htm#ASC_28
So the drive's firmware programmers were overly creative.
If it was ASCQ 0 or 2, then libburn would tol
The line with the absolute address was meant to be:
/home/chris/xorriso/xorriso-1.5.3/xorriso/xorriso -outdev /dev/sr0
-toc
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/1896804
Hi,
> libburn : SORRY : Asynchronous SCSI error on waiting after START UNIT
> (+ LOAD) [6 28 81] Drive event. Unknown ASCQ with drive event ASC 28.
Grr. A higher level intervened.
In line 198 of file
~/xorriso/xorriso-1.5.3/libburn/spc.c
there is
if (key == 0x6 && as
Hi,
well, at least we got over the strange error code.
> libburn : SORRY : Timeout exceed (3 ms). Retry canceled.
> libburn : SORRY : Command: READ DISC INFORMATION #63,[2 04 00] : 51 00
> 00 00 00 00 00 00 22 00 : dxfer_len= 34
The command READ DISC INFORMATION was retried 63 times. The la
Correction:
The single command READ DISC INFORMATION probably did not timeout, but was
repeated
with intermediate waiting until 30 seconds had elapsed. So the drive probably
reacts swiftly but
always says that it is not yet ready.
--
You received this bug notification because you are a member o
Hi,
sorry for your drive.
But good for Linux burn programs that MS-Windows does not know something
essential about drive error messages which we Linuxers don't know.
> the srange this is that if you use the Disks program in utilities.
That's probably a message from the kernel via systemd and ls
Hi,
the error message stems from the burner drive and was forwarded by libburn
to Brasero. Strangely the code ASC=21 , ASCQ=04 is not specified in in
the SCSI specs for optical drives (MMC).
In the overall error code list
https://www.t10.org/lists/asc-num.htm
it is listed for other device classe
Hi,
C. Clear wrote:
> Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10'
That would match the Debian bug of last year.
> Did try Nero for Linux and had the same
> result as I did with Brasero.
Keep in mind that in the Debian bug scenario Brasero's bad read attempt
spoiled the tw
Hi,
C. Clear wrote:
> What does doing a power off/on cycle entail ???
Just a shutdown so that the burner drive has no electrical power.
If in doubt whether the power is really off, press the drive's eject
button. The drive should not react.
Have a nice day :)
Thomas
--
You received this bug
Hi,
> > *Do you experience the problem with CD-R or CD-RW media ?*
> Yes. The exact same error message as when I tried to make a DVD.
Then it is not exactly the same problem as with the DRW-24D5MT of
Mauro Sacchetto and my BW-16D1HT as of Debian bug 998718.
Your Brasero version 3.12.1-4ubuntu2
Hi,
the initial error report of 2009 is probably due to a hardware problem
in the computers bus controller, or the cabling, or the drive's bus
controller.
> BraseroWodim stderr: CDB: 2A 00 00 01 6C 7E 00 00 1F 00
> ...
> BraseroWodim stderr: Sense Key: 0x0 No Additional Sense, Segment 11
> ...
>
Dani, your problem is not related to this old Brasero bug.
You experience problems between drive and medium after
Brasero, libburn, and the drive all accepted the medium
as suitable for writing. The drive performed two WRITE
commands before it complained about the outcome of the
third one.
Further
This narrows the set to: DVD-R, DVD-RW, DVD+R, DVD+RW.
(DVD-RAM and DVD+R DL have significantly different sizes.)
You should try a different brand of media. Best a different
type. E.g. try DVD+R if the failing ones are DVD-R.
If all reachable kinds of DVD fail, then consider to exchange
the drive.
Hi,
the drive tells libburn that the medium is not a DVD-RW
but a DVD+R. xorriso forwards this info:
> Media current: DVD+R
> Media status : is written , is closed
The perception of media type stems from "00 1b" in the reply
to the GET CONFIGURATION command
> GET CONFIGURATION
> 46 00 00 00 00
Hi,
since the problem will soon be old enough to go to school,
i propose to fix a bug in the libburn plugin of Brasero
which is to see at
https://git.gnome.org/browse/brasero/tree/plugins/libburnia/burn-libburn.c#n558
This line obviously gets a number out of brasero's state:
brasero_jo
Hi,
it is quite sure that you do not suffer from this old bug.
Please file a new bug. Tell what you did with which program,
which drive, which kind of media. Tell what error messages
you get when you try to read the discs.
Please notify me by mail to scdbac...@gmx.net about the
new bug report num
Hi,
regrettably there is no debugging facility in libisofs which one could
enable without modifying Brasero. Further the Joliet mangler of libisofs
does not produce messages even if i enable DEBUG verbosity when it runs
underneath xorriso.
The problem with libisofs is only that it does not accept
Hi,
the first message about lack of permissions is common and should be
harmless. The failure happens possibly with the attempt to get 16 MiB
of memory via call mmap(2). But it is not obvious why this only succeeds
if you are superuser.
So this might too be a red herring and the actual reason for
Hi,
Paul Menzel wrote:
> The way to solve this error, is that people provide the necessary log
> files from Brasero and to improve the things Thomas Schmitt and George
> Danchev have found out to be incorrect [1].
Well, actually we [George and me] do not have any good idea left what
g
Hi,
for completeness: One of the two Debian patches replaces
the theory of SAO-versus-TAO.
It turned out that the function, which transmits the
libisofs image data to the burn software, dropped every
second data block. (Actually the first block of each pair
of blocks.)
https://bugzilla.gnome.org
Hi,
this problem could be caused by the Brasero bug
that was found in the course of
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero i
Hi,
some technical comments to Nico Zanferrari's notes:
> (I always use a fresh standard live 32 bit USB key with the same DVD-RW)
> [...]
> - the "unreadable coasters" produced from other Ubuntu versions are seen as
> blank disk from standard brasero 12.10, and can be easily blanked with it.
> T
Hi,
there was a brasero bug fixed in the course of
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
which began by a different problem but collected several
reports about unmountable CD and DVD.
It hit data burning on-the-fly but not burning of pre-produced
ISO images or of CD audio
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 CLOS
Hi,
> As source I used the downloaded ISO of PartedMagic from 2012_11_30.
> I simply opened this with Brasero to start burning on a DVD-RW,
> which first had to be erased.
The bug that was fixed here did not affect burning of prepared
ISO images, but only composition of ISO images from hard disk
Hi,
> I was using a CD-RW, not DVD-RW, 650 MB, 4x
> I'm not sure, if -format would concern here?
Not with xorriso, and not desirable for your purpose.
> Now I tried again with just updated 3.4.1-0ubuntu1.1:
> Burning took ~ 10 min. at 4x --> successful
Some bugs were fixed in the meantime. The
Hi,
> So I was in good luck that I only had to wait 2 days for the fix :-)
I guess the fix for your problem was available since a while.
But if you had installed it, you had gotten the bug that was fixed here.
So your luck is a very wise one which knows how long to wait. Congrats.
Have a nice
Hi,
i am the developer of libburn, which would probably be in charge
for burning underneath Brasero in younger Ubuntu versions.
(One can learn from Brasero logs, whether libburn is used as
burn backend. Search for "Libburn".)
There was a bug when the application asked for minimum speed
and the f
Hi,
i am the developer of libburn, which might be employed as burn backend
by Brasero. In this case i offer my help with finding the reasons of failure.
Needed would be a tester with an affected Brasero program, the necessary
type of media, and the willingness to run experiments with command line
Hi,
i noticed that the properties of DVD-RW are misrepresented
in some of the posts.
DVD-RW can assume two states: sequential and overwritable.
The sequential state behaves much like CD-R or DVD-R. The medium
has an own table-of-content where it records the track boundaries
of one or more burn s
Hi,
To my own experience, the code which governs creation and burning of
ISO images on-the-fly is separate from the code that governs burning
of pre-produced image files from hard disk.
(I am developer of libburn and libisofs, not a user of Brasero.
But i once had reason to find out how Brasero m
Hi,
i am the upstream programmer of libisofs and libburn but not
directly involved in Brasero.
Andrea Amoroso wrote in #63:
> still the mp3 cds I burnt are full of the mp3 i chose, with some
> of them unreadable and others readable but with many lags
It is not clear to me whether libisofs was i
Hi,
Austin Dempewolff wrote:
> I'm not sure if my problem was exactly the same bug (Brasero was producing
> coasters
> without any errors,
That seems to be the much more often occuring problem, although it is
not the original cause of this bug report thread.
> but I was burning ISOs, not data C
Hi,
i wrote:
> > cdrskin -tao padsize=300k -v dev=/dev/sr0 blank=as_needed -eject image.iso
Austin Dempewolff wrote:
> Done, worked great. Stdout attached.
I assume you tested full readability afterwards.
That cdrskin command is supposed to do quite the same with libburn
as Brasero does. One d
36 matches
Mail list logo
