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 581836 - Internal error before burning process starts
Internal error before burning process starts
Status: RESOLVED FIXED
Product: brasero
Classification: Applications
Component: general
2.27.x
Other Linux
: Normal major
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-05-08 08:20 UTC by JK
Modified: 2009-08-15 13:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Logfile of the "internal error" (5.44 KB, text/x-log)
2009-05-08 08:21 UTC, JK
Details

Description JK 2009-05-08 08:20:26 UTC
Hi!

 I've recently found a bug that seems to be related to the checksum plugins. 

Steps to reproduce:

Burn some files and enable the image checksum plugin (maybe you need to start a multisession CD, not sure about this though).

Result:

Before the actual burning even starts, an internal error occurs (see attachment). 

Notes:

At first I thought that this bug may be related to bug #572840, but it's a different constellation. First of all, it happens when burning FILES and enabling the IMAGE CHECKSUM plugin (imho, in this case the plugin should not be invoked at all) and secondly, the error occurs BEFORE the burning process even starts...

Regards 

JK
Comment 1 JK 2009-05-08 08:21:30 UTC
Created attachment 134245 [details]
Logfile of the "internal error"
Comment 2 JK 2009-06-20 10:35:44 UTC
UPDATE : I've just tested the current trunk and the bug is still there. The log attached above is still valid (even the line number) so I won't attach a new one.

But I'd really like to know how the status of the bug is! It's still marked as UNCONFIRMED, but it's so easy to reproduce: enable the image checksum plugin and burn some files. Since burning doesn't even start in that case, I really consider this a major bug...

Regards

JK
Comment 3 JK 2009-08-15 08:57:20 UTC
UPDATE : I've just done some tests with the current trunk and the bug seems to be gone, at least I wasn't able to reproduce it. I wonder why it's still marked as UNCONFIRMED...

Regards

JK
Comment 4 Philippe Rouquier 2009-08-15 13:03:11 UTC
Thanks for your report and sorry for not noticing it earlier. It's still marked as unconfirmed while it was fixed because I was not aware of it.
I'm closing it and feel free to reopen it if it comes up again.

Again I apologize for not seeing it and thank you for reporting bugs.