After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 535926 - Brasero could tell the user if the CD/DVD is spinning too slowly
Brasero could tell the user if the CD/DVD is spinning too slowly
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
0.7.1
Other All
: Normal enhancement
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-05-31 14:58 UTC by Martin Ahnelöv
Modified: 2018-09-21 16:27 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Martin Ahnelöv 2008-05-31 14:58:57 UTC 
Hello! In Ubuntus bugtracker we've received a bug where a user tried to burn a DVD, but no files showed up. This was caused by a fault power supply that most likely made the DVD spin too slowly. Everything worked correctly when this was exchanged.

Could Brasero alert the user if there is a problem with the DVD's spinning speed?

Link to the launchpad entry: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/214707
Link to Brasero's error log: http://launchpadlibrarian.net/13292719/brasero-session.log

Other information:
Comment 1 joerg.schilling 2009-07-01 19:53:48 UTC 
Many DVD writers have broken firmware. Cdrecord
thus implemnents many workarounds for the broken
firmware.

If you use recent original cdrtools from:

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

and in case you do not specify a speed= parameter
to cdrecord, cdrecord will always write with the
best speed that works with the current drive/media
combination.
Comment 2 GNOME Infrastructure Team 2018-09-21 16:27:31 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/25.