Be careful: cdrdao is a security risk if installed suid root and wodim
is full if Debian specific bugs (there is e.g. no support for BluRay and
50% of all DVD writes fail).
Also note that cdrdao and wodim et. al are unsupported and unmaintained
since a really long time.
The original software is
Please note that your nore #128 mentions "growisofs" but this is a bug
that asks for re-intrgrating the original cdrtools software.
Do you like to have the original software back again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, is this an intentional status change _here_ or just an imported
status change from fedora?
Given that Ubuntu "recently" started to ship ZFS, it seems that Mark
Shuttleworth finally follows the license strategy I offered him in 2008.
This should make it obvious to include the original
Given that the GPL does not contain the term "linking" at all, there is
no difference between static and dynamic linking.
But it may be of interest that Simon Phipps (Director at OpenSource.org)
at CeBIT (March) 2009 made the following agreement with Debian:
Debian starts shipping the original
This article on "enterprise" is wrong - sorry.
What really happened is this:
In 2004, Debian decided to attack the cdrtools project, created a buggy
fork (illegally under the original name) and stopped distributing the
original software in May 2004.
After 2 years of attempts to solve this
Mr. Glaubitz is well known to spread hostile personal attacks at various places.
just search for glaubitz or cbmuser.
Matteo, your assessment was right. People with a real objection would be able to
verify their claims.
As you can read in comment #46, the problem was initiated by two people at
It seems that you are not using recent original software but an unmaintained
copy that did not get updates during the past 9.5 years.
I recomend you to upgrade to recent original software from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
the original software added support for unicode characters
You are not using recent original software but something that is unmaintained
since
May 2007. Do not expect to get any help for this dead code as the people behind
it
stopped even answering to bug reports many yearsa ago.
I recommend you to upgrade to recent original software from:
A command sequence error usually appears, when unfriendly software
interrupts the write process, ignoring the current write task.
hald and similar on Linux are known to be such software, kill it.
Another possible way to go is to write in -raw96r mode to prevent the
drive from being able to
You are not using the official software but a copy from 2004 where the working
DVD support was ripped off and replaced by some thing half baken. I recommend to
upgrade to recent original software from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
--
You received this bug notification because you
*** This bug is a duplicate of bug 213215 ***
https://bugs.launchpad.net/bugs/213215
Please note that cdrkit is not derived from a 2006 cdrtools original source
but rather
from a version from September 2004 and that the working DVD support from the
original
has been ripped off and replaced
I am not sure how I should interpret the text in comment #44. To me it
looks as if it has been written by a very unfriendly person but I am open
for a different explanation if possible...
Let me recapitulate:
In May 2004 a new and unfriendly Debian packetizer started to attack
the cdrtools
AFAIK, the ubuntu brasero version has been configured to not support the
oritiginal cdrtools.
You need to compile brasero by your own, uninstall wodim and related
commands and install the original cdrtools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just a note in case this helps:
Yesterday, I reworded the file COPYING a bit in order to avoid confusion
and to make things more obvious.
Check: ftp://ftp.berlios.de/pub/cdrecord/alpha/COPYING
in special the new top parts that explain work-limits and the enhanced
GPL notes at the end that
Well, it seems that recently some people came up with proposals that are not
realizable. Let me give some explanations on the background:
The whole problem has been initiated by an unfriendly Debian packetizer in
May 2004. At that time this person was a newcomer and the previous
Debian
Your request creates the impression that the original cdrtools are not
valid OSS.
I am sorrry to see that you are wrong.
I've received a very clear statement from Eben Moglen on that the GPL of course
permits to link GPLd software against any library of any license as this is the
requirement
Well, I'll tell you what's wrong:
The claim ...If You do, you may distribute the combined work under the
terms of the GPL.
does never apply for typical OSS projects (unless someone makes _all_ parts
available under the GPL in their repspective source), so Mantas asked me to
grant something I do
Clement told me that he likes to approach Debian at debian-
derivati...@lists.debian.org but I did not hear from him since 3 weeks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/213215
Title:
A new cdrtools version has been released, if you like to create a binary
package, please use this one.
BTW: Meanwhile, the only currently known bugreport has been verified to
be a false alarm.
For:
https://bugs.kde.org/show_bug.cgi?id=257241
the reporter send the CLI parameter to repeat the
I did not publish a new cdrtools release since june even though there is
new code (e.g. available in the schily source consolidation).
If you like to make a binary package, please contact me so I can make a new
cdrtools source release and give some advise on how to compile things the
best way
Hi Mantas,
what kind of discussion do you believe is necessary?
Cdrtools is legal OSS and thus there is no need for a contract to use
it.
As Debian did change seveal users of cdrtools with the intention to make
it hard to replace cdrkit by the original software, you may need to
remove these
Let me repeat again:
The maintainer of libcdio admits that libcdio contains code from
cdda2wav and the code crom cdda2wav is available under GPLv2-only or
under CDDL but not under different licenses. Note: this is an official
statement from the cdda2wav author.
BTW: This is not the only software
I have no idea how I could change things since the original software has no
license
problems.
Ubuntu just seem to ignore facts and instead ships dead software that even has
problems with legality.
Ubuntu obviously is not independent and is no more than a vassal of Debian that
verified that
The fork has been created together with a social attack against the
original project.
You may like to ask why Ubuntu supports the social attack instead of
supporting the original software.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Given the fact that genisoimage is an unmaintained fork from a 7 year
old mkisofs, you should not expect help from the people behind
genisoimage.
If you like help and are willing to give further information on your
problem (e.g. the data that caused the problem) it may be a good idea to
send mail
genisoimage is an unmaintained fork from a 7 year old mkisofs.
5 years ago, _many_ bugs have been fixed in the original mkisofs.
Did you try a recent original cdrtools:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
P.S. do not expect a fix in genisoimage.
--
You received this bug notification
Nobody is violating a license for distributing cdrtools either in source
or in binary form.
If you believe the people who claim that there is a problem, then Ubuntu
as a whole would be undistributable as Ubuntu is full of similar
constructions.
I had a discussion with Till Jaeger (the most well
Do you really use mkisofs or do you use the defective fork genisoimage
from Ubuntu?
You should call: mkisofs -version and check the output.
If you are using correct software, you get something like:
mkisofs 3.01a05 (i386-pc-solaris2.11) Copyright (C) 1993-1997 Eric
Youngdale (C) 1997-2010
If Ubuntu did not distribute the illegal cdrkit, I would fully agree
with you.
Please note that I as the Copyright holder also need to admonish people
or companies that do not follow a legal path and Ubuntu is in not on a
legal path because they publish cdrkit.
On the other side, users like
Wodim is a dead fork from a cdrecord version from September 2004. It includes
not only
the bugs could be found in cdrecord in 2004 but also plenty of bugs that have
been added
by the fork.
I recomment do upgrade to recent original software:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
The bug is a result from not using the original cdrtools software.
The original software supports to write all media types but in the fork
distributed on Ubuntu, the DVD support code was ripped off.
The best solution is to upgrade to the original software retrieved from
daf: Unfortunately Debian did break their promise after trying to delay
a definitve action for a long long time.
Fortunately, there are other users that are unhappy with the problems in
cdrkit and created a Ubuntu binary package.
--
You received this bug notification because you are a member of
Chris Bainbridge comment is irrelevant, he does not seem to know the
legal facts.
The creation if the fork cdrkit (wodim, genisoimage, et. al.) is a result
of a social
attack from a Debian packetizer against the cdrtools project. The person who
started this
attack never has been interested in
You unfortunately do not describe your problem in a way that would allow
to understand the reason.
genisoimage is based on a more than 6 year old cdrtools version with additional
bugs (specific to the fork) added. You cannot expect such an old and
unmaintained
software to support large files
There are several cdrtools packages available as PPA, search e.g. for
brandonsnider
--
Brasero, Nautilus Write to Disk, and Xcdroast all require cdrecord
https://bugs.launchpad.net/bugs/618963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The final version has been published now:
ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-3.01a01.tar.bz2
--
Ubuntu 10.10 writes corrupted Blu-Ray BD-R
https://bugs.launchpad.net/bugs/678294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So you are a victim of hald or a more recent replacement of hald.
It would be better to write in RAW mode in your case and writing in
RAW mode also prevents hald or similar to disturb the write process.
BTW: I did just put out a newer version of cdrtools that fixes a problem
that is seen when
There is a really simple solution for your problem: Install revent
original software.
The problem you describe has been fixed 4 years ago.
--
genisoimage error directories too deep using Rock Ridge
https://bugs.launchpad.net/bugs/135362
You received this bug notification because you are a
If the medium really does not carry a ISO-9660 based filesystem, then
isoinfo is the wrong program.
In any other case, your problem is expected to be a result of the fact
that Ubuntu does not distribute the real isoinfo command but a broken
fork that has been created from a 6 year old cdrtools
The problem you see, has a social background and you need to find a way to
deal with the social problems introduced by Debian before your technical problem
will be fixed. Unfortunately even Ubuntu neither seems to care about its
users
nor about legality.
The problem has been introduced im May
cdrkit is an extremely outdated software. It offers a development state
from September 2004 with additional bugs added by the cdrkit team. The
software did get major enhancements and bug fixes since then, but this
has been completely ignored by Ubuntu.
As Ubuntu does not offer recent legal
The original software did never use the broken UTF-8 patch that is the
reason for the buggy behavior of the fork on Ubuntu.
The original software introduced a working UTF-8 solution in Auhust
2006.
I recommend to use the original software (current release is
cdrtools-3.00) as it correctly
If you do this, you need to make sure to remove anything from
wodim/cdrkit from your system, as it may be that the software has been
modified to use the fork instead of the original even in case the
original software is available.
--
blank=fast operation never finishing (Sony CD-RW)
I recommend to try recent original software (cdrtools-3.00).
Wodim is known to have many bugs and it is unmaintained.
If cdrecord fails also, then you are a victim of hald.
--
wodim reports Errno: 5 ... and cdrw keeps spinning
https://bugs.launchpad.net/bugs/645050
You received this bug
Wodim is unmaintained and known to be buggy.
Did you try to use recent original software (cdrtools-3.00)?
--
blank=fast operation never finishing (Sony CD-RW)
https://bugs.launchpad.net/bugs/637684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
wodim does not really support to write DVDs.
I recommend to use the original software instead:
http://cdrecord.berlios.de/
The original software is maintained and knows about firmware bugs from
the various drives.
--
Low Burning Speed
https://bugs.launchpad.net/bugs/618468
You received this
It seems that you missunderstand two constraints:
- There is no development in Ubuntu, so proposing source changes here
are unlikely to have any affect.
- Applying the changes you propose would result in giving up
portability.
--
code maintainability, modularity and readability issues
On Friday noon, Marc Shuttleworth is in Berlin at the Linux Tag.
I believe it would be a good place to ask him why he is so stubborn
and prevents legal working software from appearing in Ubuntu.
--
cannot burn ISO images to CDs
https://bugs.launchpad.net/bugs/590522
You received this bug
In any case, it is wrong: You cannot fix a nonexisting problem.
Cdrtools of course is distributable.
...and Ubuntu still distributes a buggy, dead and undistributable fork
instead of original software :-(
--
cdrtools is undistributable
https://bugs.launchpad.net/bugs/177154
You received this
Well, you unfortunately did not send any information on your
recent problem, so I cnnot even see whether you use cdrecord.
--
Can't write or format DVD-RW in Ubuntu Hardy
https://bugs.launchpad.net/bugs/329096
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Use the official cdrtools from:
http://cdrecord.berlios.de/
Make sure to use a recent version (e.g. the one released on May 17th),
There are of course several binary .deb packages that also deliver
cdrtools.
--
Can't write or format DVD-RW in Ubuntu Hardy
Ubuntu unfortunately does not distribute the original software.
Your problem will not be resolved the way you hope.
Please note that cdrecord -v is not sufficient, if you like to write
to a medium, you at least need to add a file name for a file
with a related ISO filesystem image.
--
Can't
If you like to get help, please send the output from cdrecord -v
--
Can't write or format DVD-RW in Ubuntu Hardy
https://bugs.launchpad.net/bugs/329096
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
You are not using cdrecord but a defective fork called wodim.
wodim is a dead fork from a 5 year old version of cdrecord with
bugs added that never have been in the original.
The device or resource busy message is a result from such a bug.
Note that you also do not use mkisofs but genisoimage
The unknown error log includes a hint that wodim, a fork
from cdrecor with many well known bugs aborted.
Did you try the original software?
--
unknown error ocurred while burning a CD-RW with brasero
https://bugs.launchpad.net/bugs/413823
You received this bug notification because you are a
You should send your bug report to the Linux kernel folks!
Note that this kernel bug has been reported many times during
the past few years.
When I did first see this Linux kernel bugs in 2004, the Linux kernel
folks did not show any interes in tying to fix it
The bug seems to cause the
Even though the people from Debian who created the cdrtools fork
called cdrkit advertize for nero, nero is non-free and closed source.
Using nero does not help us the OSS people
Note that wodim does not contain working DVD support code. The working
original code from cdrecord that has been
The fork genisoimage is full of bugs and based on a 5 year old mkisofs
version. Genisoimage is (like the whole fork from Debian) unmaintained
since May 2007.
I recommend you to use recent original software from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
--
You are not using cdrecord but a defective fork called wodim, so you
definitely
do not have a problem caused by cdrecord or cdrtools.
I recommend you to first upgrade to recent original software:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
The problem is that ubuntu by default does not install the original software but
the broken fork. When you call cdrecord on ubuntu, you don't get cdrecord :-(
--
Burned iso image corrupted
https://bugs.launchpad.net/bugs/556595
You received this bug notification because you are a member of
This problem is caused by the fact that you are not using the real cdrecord
but a defective fork.
In special, there is absolutely no support for DVD Dual layer media in
the fork.
Get the real program:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de
or as a ubuntu package
I cannot speak for unknown bugs that probably are in genisoimage. Let me
therefore
only mention known bugs. It is unlikely that the quoted error message from
genisoimage is related to specific characters in the file names.
It may have two different reasons:
1) An incorrect commandline forces
This verifies that the problem was caused by a bug in hald.
You should open a bug against hald
--
Can't burn CD's using any tool
https://bugs.launchpad.net/bugs/531901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
We just verified that your problem is not caused by cdrecord but by
hald.
I reassigned this bug to hald.
** Package changed: cdrtools (Ubuntu) = hal (Ubuntu)
** Changed in: hal (Ubuntu)
Status: New = Confirmed
--
Can't burn CD's using any tool
https://bugs.launchpad.net/bugs/531901
I am not sure whether you killed the right hald process.
Please note that every media that is written to and interrupted by hald
will turn unusable.
If you don't know which hald process to kill, I recommend to just add the
option -raw96r
to cdrecord.
--
Can't burn CD's using any tool
As the build system of the fork cdrkit frequently causes problems
and as there are many bugs in the fork that don't get fixed, wouldn't it
be obvious to use the working original software instead?
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
--
cdrkit ftbfs on all
You are not using cdrecord but a buggy and illegal form from a very outdated
version of cdrecord.
I recommend you to get a recent version of the original software from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
Make sure to
You did still not use cdrecord but the fork wodim.
You may need to remove the wodim binary and to manually create a
link to the original software.
See http://cdrecord.berlios.de/private/linux-dist.html for information
on how to identify the original software.
--
Can't burn CD's using any tool
OK, you did now call cdrecord.
Please call:
ps -efc | grep hald
and later call
kill -STOP PID
where PID is the pid you see from the ps command.
Then try to write again.
After you did write, you may call kill -CONT PID
--
Can't burn CD's using any tool
It is usually the first number.
BTW: if you have something like pgrep, just call:
kill -STOP `pgrep hald`
--
Can't burn CD's using any tool
https://bugs.launchpad.net/bugs/531901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If you have problems writing CDs that are a result of a missbehaving hald, it
usually
helps to use cdrecord -v -raw96r ...
If you write in raw mode, even the drive does not know what's happening and the
wrong algorithm in hald does not get the trigger that is otherwise usually
missinterpreted
It is a well known fact that wodim does not support to write DVDs correctly.
With other DVD media types, it may work under some conditions but DVD Dual
layer media does not work at all when using wodim.
This is a result from removing the mature DVD support in the original cdrecord
and replacing
I have a 'MATSHITA' 'BD-MLT SW-5582 ' BluRay writer and this definitely
supports
to write CDs in RAW mode.
So far, I havn't seen any modern CD-writer that does not support RAW
mode.
As wodim is just an unmaintained fork from a very old cdrecord and as the
fork has just been created by some
This bug report is not against cdrecord but against a broken fork.
The specific problem mentioned in the bug report has never been
in cdrtools (the original software). The problem mentioned in the
bug report results from incorrectly interfacing to hald in the fork.
I recommend you to install
It seems that your problem is that wodim does not permit your
drive media combination. I recommend you to upgrade to
recent original software from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
The original cdrtools software is well maintained...
--
cant blank
You are not using cdrecord but wodim. You thus cannot expect that
writing to DVDs works at all.
wodim is a fork made from a more than 4 year old cdrecord version
by adding plenty of bugs and by replacing the mature DVD support
from the original cdrecord by something half baken. Note that if you
You are not using cdrecord but wodim. You thus cannot expect that
writing to DVDs works at all.
wodim is a fork made from a more than 4 year old cdrecord version
by adding plenty of bugs and by replacing the mature DVD support
from the original cdrecord by something half baken. Note that if
Thank you for this report!
Could the reason for your problem a result of using a modified k3b that
probably has been told not to search for cdrecord?
--
k3b does not see/use alternative programs ins /opt/schily/bin
https://bugs.launchpad.net/bugs/493718
You received this bug notification
k3b is only a frontend to write programs. Which program has been used to write
to the medium and what error occurs?
--
K3b burnt a data dvd but that disk can't be recognized by any dvd device
including the burner itself
https://bugs.launchpad.net/bugs/467978
You received this bug notification
genisoimage does not support files 4 Gb. genisoimage is unmaintained
since nearly 3 years, don't expect your problem to be fixed in genisoimage.
I recommend to use the original cdrtools software as cdrtools is actively
maintained and as there are no known bugs in cdrtools.
--
Cannot burn files
The original problem has not been fixed:
- it is even worse now as the current libcdio is published under a supposed
GPLv3 or
any later while it contains code that was published under GPLv2 only.
The authors of the related code have not been asked and would not give their
OK
for a license
It is wrong not to use the bus id's. This has been in the documentation
since 1996 and this did never change. The person who created the fork
wodim just does not understand the constraints in the Linux kernel and
gives wrong advise.
As mentioned above already, wodim is a defective fork from an
And this is again a problem that disappears if you
upgrade to recent original software from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
instead of using an unmaintaned fork.
--
Cannot open SCSI driver!
https://bugs.launchpad.net/bugs/503186
You received this
Be careful! cdrdao does not support all features in CUE files.
Cdrecord is a better choice:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
--
Brasero fails to burn cue/bin file due to missing -dao within wodim
https://bugs.launchpad.net/bugs/497048
You received this bug
You are not using original software but a buggy and legally undistributable
fork that has been created by a hostile downstream.
If you look at the bug tracking system of the various Linux distributors that
do not distribute the original software, you will find more than 100 bugs
that are
cdrkit is unmaintained since May 6th 2007, don't expect any fix anytime
soon.
If you like to use working software just use the original software.
--
cdrecord maps bus,target,lun to /dev/sgX imperfectly
https://bugs.launchpad.net/bugs/23203
You received this bug notification because you are a
As Ubuntu unfortunately still distributes the fork cdrkit
instead of the original software, there is no hope for a
fix.
--
mkisofs aborts on malformed joliet filenames
https://bugs.launchpad.net/bugs/23046
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
The fork is using a non-cooperative packaging. It may be that
you need to remove the files wodim, genisoimage and similar
by hand and after installing the original software create symlinks
with the names from the fork that point to the original software.
For a long term solution, you could ask
Your problem is a result from using the unmaintained fork wodim
instead of the original software..
Just upgrade to the original software from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
and your problem will go away.
--
brasero failed to burn cause drive was
It could be interpreted as advertisement if you had the choice...
It is however not an issue of choice as Ubuntu does not give users
the chance to chose between the buggy illegal fork and the
maintained legal original software.
Ubuntu has chosen the illegal way and it is my right as the
Copyright
You mention an important issue with genisoimage. Genisoimage does
not implement correct UTF-8 support. What's in genisoimage is just
a bad hack as only 50% of the places that need UTF-8 support have
been addressed and even these parts have bugs. The original
mkisofs includes complete and correct
It seems that you missunderstand the situation. What Ubuntu installs
under the name mkisofs is not mkisofs but a fork made from a completely
outdated version with many bugs added and with many features missing.
Ubuntu does not have the permission to install something that is not
the real mkisofs
Mkisofs of course has a man page, see:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
BTW: Ubuntu does not install mkisofs but an outdated dead fork
called genisoimage
--
mkisofs has no manpage
https://bugs.launchpad.net/bugs/489077
You received this bug
Unfortunately it is not. You need to get the original software yourself
from the location named above.
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You did not attach the error messages from the write process,
so I may only guess for the most probable reason.
As you mention cdrecord, you should know that Ubuntu
does not distribute cdrecord but a fork called wodim that has
been made from a 4 year old version of the original software.
This
What do you expect from such a feature?
Should this feature be compatible with the overall design of mkisofs?
There is a patch that definitely is not compatible with the design of
mkisofs as the patch will not work with mkisofs ... | cdrecord
Mkisofs is designed to work completely without
Did you only install cdrecord or did you also use it for tests?
--
Wodim 1.1.9 stops burning to DVD after a few seconds
https://bugs.launchpad.net/bugs/477321
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
-vv does not give helpful new information in your case.
The SCSI command timeout for the write commands for
a DVD is 100 seconds. If sending a kill signal does not
show any result after 100 seconds, there must be a kernel bug.
Even though, your problem may be caused by a cable
problem (that
You are not using cdrecord but a defective fork from a very old version.
The fork was created by a hostile downstream who is missing the needed
skills for SCSI programming. The fork was given up on May 6th 2007.
There are more than 100 well known problems in the fork (most of them
did not exist
Sorry for the typo, it should read:
All drives I've seen did support RAW writing
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
1 - 100 of 273 matches
Mail list logo
