desktop-packages team mailing list archive

[NoOp <367037@xxxxxxxxxxxxxxxxxx>]

Regarding comment #24: This is not a 'false alarm' but actually may not
be related to brasero.

In performing several tests related to:
<https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/691482>
[Brasero Disc Burner > wrongly named]
I encountered the checksum errors. Sample:

BraseroReadom disconnecting BraseroReadom from BraseroChecksumImage
BraseroReadom deactivating
BraseroChecksumImage called brasero_job_get_current_track
BraseroChecksumImage Setting new checksum (type = 2)
631bb631ab92d6b965051b4b42346158 (a2c9eb7d63f603b6f9ae4b3deb3d2d48 before)
BraseroChecksumImage called brasero_job_error
BraseroChecksumImage finished with an error
BraseroChecksumImage asked to stop because of an error
	error		= 27
	message	= "Some files may be corrupted on the disc"
BraseroChecksumImage stopping
BraseroChecksumImage closing connection for BraseroChecksumImage
Session error : Some files may be corrupted on the disc
(brasero_burn_record brasero-burn.c:2862)

However, when burning a CD using the exact same files using brasero
(rather than CD/DVD Creator offered in nautilus) as a 'Data disc' the
operation & burn works fine (with the exception of brasero's failure to
eject the disc properly
(https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/519935). So it's
possible that complaints regarding brasero may actually be related to
the nautilus CD/DVD Creator application instead.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/367037

Title:
  Error while burning - some files may be corrupted on the disc

Status in A disc burning application for gnome 2:
  New
Status in OEM Priority Project:
  Triaged
Status in “brasero” package in Ubuntu:
  Triaged

Bug description:
  brasero 2.26.0- this is happening after burning, but burned disk
  (DVD/CD) is "OK" so I send you an screen-shot and a brasero-
  session.log file, so you can see what is happening, I think I get this
  bug is because brasero check the file on the disk after ejected

To manage notifications about this bug go to:
https://bugs.launchpad.net/brasero/+bug/367037/+subscriptions