Creating silly control sum

Bug #870581 reported by robert leleu
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Brasero>Graver une image-disque>ubuntu-11.04-desktop-i386-fr.iso>Vitesse maximum/Utiliser burnproof>Gravure>Effacer le disque actuel>
Création de la somme de contrôle pour l’image>Effacement>Écriture de la piste 01>Fermeture du disque>Succès> Création de la somme de contrôle pour l’image:(letemps restant estimé décroit de 00:08:01 à 00:01:01, puis croit, apparemment sans limite.
Annulation

Creating the control sum after burning and lagging seems silly, isn’t it ?

However the CD is OK

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic-pae 2.6.38.8
Uname: Linux 2.6.38-11-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Oct 8 11:30:47 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
 LANGUAGE=fr_FR:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: brasero
UpgradeStatus: Upgraded to natty on 2011-05-04 (157 days ago)
XsessionErrors:
 (thunderbird-bin:2006): Bonobo-WARNING **: Bonobo must be initialized before use
 (gnome-panel:1982): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x9ac5700
 (gnome-panel:1982): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x9ac5700
 (thunderbird-bin:2592): Bonobo-WARNING **: Bonobo must be initialized before use
 (firefox:2668): Bonobo-WARNING **: Bonobo must be initialized before use

Revision history for this message
robert leleu (robert-jean-leleu) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in brasero (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for brasero (Ubuntu) because there has been no activity for 60 days.]

Changed in brasero (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Elbarbudo (patricearnal) wrote :

The bug is still here on Brasero 3.12.2

Changed in brasero (Ubuntu):
status: Expired → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.