Brasero reports incorrect drive speed

Bug #371002 reported by Scott Armitage on 2009-05-02
52
This bug affects 9 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: brasero

Ubuntu 9.04 (Jaunty)
Brasero 2.26.1-0ubuntu1

When burning data DVDs, Brasero reports an estimated drive speed of ~350 KiB/s (0.3x), however from the progress bar, estimated time remaining, and total data written, the drive is clearly operating in the 3.5 MiB/s range.

This occurs predictably every time I burn a data DVD. See the attached screenshot.

Scott Armitage (scott-armitage) wrote :
Scott Armitage (scott-armitage) wrote :

Note: this bug may be related to bug 371002.

Scott Armitage (scott-armitage) wrote :

D'oh.. I meant it may be related to bug 370999.

Nizar Kerkeni (nizarus) wrote :

same problem with jaunty 64bits

Changed in brasero (Ubuntu):
status: New → Confirmed
Schily (schilling-fokus) wrote :

The report does not contain useful related information but
there are some drives that report the write speed incorrectly.

Cdrecord includes many workarounds for bad drive firmware...

Get a recent cdrtools source from:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

Scott Armitage (scott-armitage) wrote :

Schily, you say the report does not contain useful information.. We have multiple people here experiencing the same problem. Perhaps you could indicate /what/ would be useful information that is missing, and I am sure many of us would be more than willing to provide said information.

-S

Schily (schilling-fokus) wrote :

Well, it is unclear how brasero gets the write speed.....

Wodim is known to be broken, so in case brasero calls wodim
an incorrectly reported speed is expected. This could be verified
by removing wodim and installing cdrecord instead.

Cdrecord knows workarounds for firmware bugs in most drives
and retrieves the correct write speed. This should visible be in the
cdrecord output.

If the brasero printout stays wrong, this is a brasero bug.
Brasero is written in a non-portable way and tries to send own SCSI commands.
Brasero should rather call cdrecord and parse the output as cdrecord works
on any recent OS.

fpissarra (fredericopissarra) wrote :

This is an official patch?

Schily (schilling-fokus) wrote :

What do you understand by "official"?

Changed in brasero (Ubuntu):
importance: Undecided → Low

I support Schily. I think this problem would be fixed when Ubuntu switched back to cdrecord in stead of using wodim. See http://cdrecord.berlios.de/private/linux-dist.html I switched to current cd record with K3b as a front end. Works perfectly and it shows the right writing speed!

alejandro (nosferatu2011) wrote :
Download full text (11.2 KiB)

Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1744)
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_set_output_size_for_current_track
BraseroBurnURI stopping
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_session_output_size
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_current_track
BraseroBurnURI burn:// URI found burn:///Unsaved%20Document%201
BraseroBurnURI called brasero_job_set_current_action
BraseroBurnURI called brasero_job_get_current_track
BraseroBurnURI Information retrieval for burn:///Unsaved%20Document%201
BraseroBurnURI Added file /home/david/Unsaved Document 1 at /Unsaved Document 1
BraseroBurnURI called brasero_job_add_track
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI Finished track successfully
BraseroBurnURI stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_set_output_size_for_current_track
BraseroLocalTrack stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_session_output_size
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_current_track
BraseroLocalTrack no remote URIs
BraseroLocalTrack stopping
BraseroChecksumFiles called brasero_job_get_output_type
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_set_output_size_for_current_track
BraseroChecksumFiles stopping
BraseroChecksumFiles called brasero_job_get_output_type
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_session_output_size
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_set_current_action
BraseroChecksumFiles called brasero_job_get_flags
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles Adding graft for checksum file /.checksum.md5 file:///tmp/brasero_tmp_PZC73V.md5
BraseroChecksumFiles called brasero_job_add_track
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles Finished track successfully
BraseroChecksumFiles stopping
BraseroChecksumImage called brasero_job_get_current_track
BraseroChecksumImage called brasero_job_get_action
BraseroChecksumImage called brasero_job_get_flags
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs creating input
BraseroGrowisofs getting varg
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_current_track
BraseroGrowisofs called brasero_job_get_fd_in
BraseroGrowisofs got varg:
BraseroGrowisof...

jgv (visserjg) wrote :

Reported in 2009! Not a solution yet (2013)?

Gergely Csépány (cheoppy) wrote :

I don't have an optical drive any more, maybe others have also got rid of them too, and there's no one left to trace down this bug. :)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments