Brasero always burns CD/DVD at max speed (speed option is ignored)

[Bartosz Woronicz]

Binary package hint: brasero

The disc I tried is Verbatim CD-RW 1-4x speed. The option are given to burn, 4,8,10.MAX. I choose 4, but still burns up to 10.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: brasero 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Oct 7 13:45:54 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.utf8
 SHELL=/bin/bash
SourcePackage: brasero

[Daniel van Vugt (vanvugt)]

Confirmed this is still a problem in natty with:

ii brasero 2.32.1-0ubuntu2 CD/DVD burning application for GNOME
ii brasero-cdrkit 2.32.1-0ubuntu2 cdrkit extensions for the Brasero burning application
ii brasero-common 2.32.1-0ubuntu2 Common files for the Brasero CD burning application and library
ii libbrasero-media1 2.32.1-0ubuntu2 CD/DVD burning library for GNOME - runtime

Screenshots to follow...

[Daniel van Vugt (vanvugt)]

This bug has been reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=637235

[renbag (renbag)]

Confirmed also for DVD-R and DVD-RW writing.

[ginalfa (ginalfa)]

I can confirm this bug in natty for CD and DVD

[kassych (kassych)]

Yep, its a bug alright.. I realized 3 DVD's later :(

[FernanAguero (fernan-ciudad)]

Confirmed on Natty. Speed setting is ignored.

As a workaround you can use wodim(1) on the command-line, until this gets fixed. In this case the speed setting is acknowledged.

wodim dev=/dev/cdrw speed=4 -v image.iso

See https://help.ubuntu.com/community/CdDvd/Burning#Command Line (Terminal)

[Mantas Kriaučiūnas (mantas)]

I can confirm this bug with latest Ubuntu (11.10) and LinuxMint 12 - Brasero always burns CD/DVD at max speed (speed option is ignored).

[zmedia (z-media)]

I can confirm this bug in Ubuntu 10.10-11.10
Brasero always burns CD/DVD at max speed (speed option is ignored)

*-cdrom
                description: DVD-RAM writer
                product: DVD+-RW AD-7580S
                vendor: Optiarc
                physical id: 1
                bus info: scsi@2:0.0.0
                logical name: /dev/cdrom
                logical name: /dev/cdrw
                logical name: /dev/dvd
                logical name: /dev/dvdrw
                logical name: /dev/scd0
                logical name: /dev/sr0
                version: FD06
                capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
                configuration: ansiversion=5 status=nodisc

[rueffer01 (rueffer01)]

I can confirm this bug in Ubuntu 12.04 beta.
Brasero always burns all kinds of CDs/DVDs at max speed, the speed option one can set is allways ignored.

Will now do some testing with the final release and comment later on it...

[LAZA (laza74)]

Bug is also in released Precise 64 bit!

XUbuntu 12.04
Linux bloedbommel3 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Brasero 3.4.1-0ubuntu1

[paolode (paolo-debortoli)]

hi. i am using ubuntu 12.04 on hp pavilion laptop with this optical unit:: scsi 3:0:0:0: CD-ROM Optiarc DVD RW AD-7581A BH05 PQ: 0 ANSI: 5 cdrom: Uniform CD-ROM driver Revision: 3.20 sr 3:0:0:0: Attached scsi CD-ROM sr0. brasero manages very well cds, but doesn't burn correctly dvds (it is like it enters in an infinite cycle; stopping it, it gives error messages, cannot closing disk or eject it) and doesn't recognize double face dvds (recognized as single face). I installed k3b and everything worked well.

[Thomas Schmitt (scdbackup)]

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 firmware of the burner drive incorrectly answered
to the SCSI command that inquires the number of offered
speed values. That bug is fixed in libburn-1.2.8.

I cannot say whether Brasero did ask libburn for minimum speed
rather than for a particular speed value. If it did, then the
libburn bug would explain the use of maximum speed.

But given the original report, that Brasero offered speed 10
for CD-RW with label "1-4x" and that the user has chosen "4",
i doubt that Brasero triggered the libburn bug.
Possibly in 2010 it still used wodim a burn backend for CDs
and growisofs for DVDs.

In case the bug still persists, i offer my help with investigating
Brasero's doings. I am not a user of Brasero myself and my Debian 6
test machine has quite an old version installed. (It is not easy
to upgrade Brasero without upgrading the operating system.)

I would need a tester who has a much newer version of Brasero.
Further we would have to find a publicly readable repository
with the source code of that Brasero version.

Advise from Ubuntu experts would be welcome in this case.

----------------------------------------------------------------

The youngest post of 2013-01-20 by paolode does not look like a
speed problem:
> doesn't burn correctly dvds (it is like it enters in an infinite cycle;

If libburn is involved as backend, then i would propose to do
experiments with my own command line burn applications cdrskin
or xorriso which can report the commands and replies of the SCSI
dialog between libburn and burner drive.

Both are offered by Ubuntu using the same libburn version as Brasero.
If newer versions are needed for the test, then it should make few
problems to compile them without disturbing the installed dynamic
libburn. (Installing libburn.so from source will probably need an
Ubuntu expert.)

If libburn is ok - which i assume - then one would again have to
inspect the source code of Brasero for the way how it uses libburn.
Possibly one will have to insert the libburn call which enables
the SCSI log. This will require recompilation of Brasero which
might become an adventure on its own.

----------------------------------------------------------------

I am now subscribed to this Ubuntu bug report 656297.
You may also contact me via <email address hidden> .

Have a nice day :)

Thomas

[zpop (zhpopivoda)]

Same problem in Ubuntu 12.04.2 and Linux Mint 13.

Brasero always burns all kinds of CDs/DVDs at max speed.

[Philip Gardner (thoatswold)]

I can confirm that the problem is still the same in Ubuntu 13.04. I can't believe that such a major bug in an application that's installed by default has gone uncorrected for so long!

[Thomas Schmitt (scdbackup)]

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_job_get_rate (BRASERO_JOB (self), &rate);

This line hands over the number to libburn as read speed,
and orders maximum write speed by value 0:

    burn_drive_set_speed (priv->ctx->drive, rate, 0);

It should obviously be

    burn_drive_set_speed (priv->ctx->drive, 0, rate);

Quoting my predecessors and myself from
  http://libburnia-project.org/browser/libburn/trunk/libburn/libburn.h

  /** Sets drive read and write speed
      Note: "k" is 1000, not 1024. 1xCD = 176.4 k/s, 1xDVD = 1385 k/s.
            Fractional speeds should be rounded up. Like 4xCD = 706.
      @param d The drive to set speed for
      @param read Read speed in k/s (0 is max, -1 is min).
      @param write Write speed in k/s (0 is max, -1 is min).
  */
  void burn_drive_set_speed(struct burn_drive *d, int read, int write);

As we are at it, how about a log line like this one ?

  BRASERO_JOB_LOG (BRASERO_JOB (self), "Setting libburn write speed to %d", rate);

Now: Arise ye users from your slumber, and get some Ubuntu maintainer
to verify my findings, to install a patch and to report upstream.

Have a nice day :)

Thomas

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.