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 572840 - Session error : An internal error occured (brasero_burn_record burn.c:2599)
Session error : An internal error occured (brasero_burn_record burn.c:2599)
Status: RESOLVED DUPLICATE of bug 591881
Product: brasero
Classification: Applications
Component: general
2.25.x
Other All
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-02-23 11:17 UTC by Savvas Radević
Modified: 2009-08-22 11:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
brasero-session.log (78.78 KB, text/plain)
2009-02-23 11:18 UTC, Savvas Radević
Details
Internal error when burning CD image with checksum plugin enabled (24.88 KB, text/plain)
2009-03-07 13:53 UTC, JK
Details
brasero-session.log (118.43 KB, text/plain)
2009-08-16 06:43 UTC, vasdi
Details
"brasero -g" output (310.65 KB, text/plain)
2009-08-16 06:45 UTC, vasdi
Details

Description Savvas Radević 2009-02-23 11:17:35 UTC
Please describe the problem:
I burn data files/folders on a DVD media, the burn reaches 99% and returns a session error.

Checking session consistency (brasero_burn_check_session_consistency burn.c:1905)
Session error : An internal error occured (brasero_burn_record burn.c:2599)

I think it's because of "File checksum" plugin.

Steps to reproduce:
Insert an empty DVD media (DVD rewritable or normal DVD)

1. Open brasero
2. Choose Data project / Create a data CD/DVD
3. Drag & drop files and folders from nautilus
4. Click Burn
5. Checked: Increase compatibility with Windows systems
6. Click Properties > Checked: Use burn proof


Actual results:
An error pops up and the DVD burning is reported as failed.
However, the DVD is actually burned successfully.

Expected results:
This error should not be shown, or be more informative.

Does this happen every time?
Yes, every time with a new Data project in Brasero.

Other information:
Enabled plugins:
- CD/DVD Creator Folder
- File checksum
- Image checksum
Comment 1 Savvas Radević 2009-02-23 11:18:41 UTC
Created attachment 129307 [details]
brasero-session.log
Comment 2 JK 2009-03-07 13:51:24 UTC
Hi!

 I can confirm this bug with the current trunk (SVN Rev.2053). It happens to me when burning a CD image with the "image checksum plugin" enabled. If I disable it brasero works as expected. 
 I think it's about the third bug related to one of the checksum plugins that I've reported. I hope that these plugins will finally become stable because imho ensuring data integrity is a very important part of every burning application...

Regards
JK
Comment 3 JK 2009-03-07 13:53:53 UTC
Created attachment 130235 [details]
Internal error when burning CD image with checksum plugin enabled
Comment 4 Cliff 2009-06-22 22:25:36 UTC
I am trying to burn an ISO to a CD and am also getting the error message.  Brasero worked fine until upgrading to Jaunty 64bit.  From Intrepid 64 bit.
Error message
BraseroChecksumImage called brasero_job_get_current_track
BraseroChecksumImage Setting new checksum (type = 2) 2602036235674bdd37d297dadd7547dd (66fa77789c7b8ff63130e5d5a272d67b before)
BraseroChecksumImage called brasero_job_error
BraseroChecksumImage finished with an error
BraseroChecksumImage asked to stop because of an error
error = 24
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 burn.c:2599)"
Comment 5 vasdi 2009-08-16 06:43:43 UTC
Created attachment 140865 [details]
brasero-session.log
Comment 6 vasdi 2009-08-16 06:45:26 UTC
Created attachment 140866 [details]
"brasero -g" output
Comment 7 Benjamín Valero Espinosa 2009-08-22 11:38:39 UTC

*** This bug has been marked as a duplicate of bug 591881 ***