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 336984 - A burning that failed does not pop a message about failure
A burning that failed does not pop a message about failure
Status: RESOLVED DUPLICATE of bug 125470
Product: nautilus-cd-burner
Classification: Deprecated
Component: cd-burner
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-02 23:36 UTC by Hubert Figuiere (:hub)
Modified: 2006-04-26 17:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Hubert Figuiere (:hub) 2006-04-02 23:36:55 UTC 
My CD burning failed from Nautilus and all I got is a message asking me to insert a new CD for at least XXX MiB. It didn't tell me that it failed.

For a clueless user, this is not a good message.
Comment 1 Fabio Bonelli 2006-04-03 11:27:10 UTC 
Hello Hubert,

It would be great if you can reproduce this with debug enabled (enabling /apps/nautilus-cd-burner/debug via gconf) and paste here the output.
Comment 2 Hubert Figuiere (:hub) 2006-04-03 13:43:01 UTC 
Oh, you have a reciepe to make CD burning fail ? I don't. I try avoid it.
Comment 3 Fabio Bonelli 2006-04-03 14:03:43 UTC 
Hubert, there's no need to be rude.

Just use a CD-RW (that way you don't have to throw a disc) and try an artificial way to reproduce the problem.

If you suspect the problem was a buffer underrun, you can disable burnproof and try to load the system.
Or, if you think (for example) cdrecord crashed, you can try with killall -11 cdrecord.

Thank you.
Comment 4 Hubert Figuiere (:hub) 2006-04-03 14:25:01 UTC 
the problem is not that it failed. the problem is that the message is completely stupid.

And I don't have a CD-RW either.
Comment 5 William Jon McCann 2006-04-19 13:55:15 UTC 
So the burn failed and you tried it again?  If so, then the message appears because the disc in the drive is not blank.  That should be expected.

The lack of notification of failure is because in most cases cdrecord does not give any indication if a burn succeeded or failed.  We hope to add burn verification before 2.16 that should help workaround this problem.

To be able to fix the specific reason for your failure we will need the debug output as Fabio has said.  Thanks.
Comment 6 Hubert Figuiere (:hub) 2006-04-19 16:08:59 UTC 
No. The message appeared at the end of the burn before me doing anything. I removed the coaster from the drive, put a new one and it did work.

As for debug the output, I'll activate debug for next time this occur. I burn CDs pretty ofte, but so far that is the first time this happpened.

Note that I don't expect the burn process to be full proof. I just expect that the user feedback be sane in these case. And yes, I know how bad cdrecord it.
Comment 7 William Jon McCann 2006-04-19 17:53:32 UTC 
So, in fact the only thing we can do for this case is attempt to verify the results.

*** This bug has been marked as a duplicate of 125470 ***
Comment 8 William Jon McCann 2006-04-26 17:56:13 UTC 
FYI, n-c-b in CVS HEAD should be able to identify when a burn fails and report an error dialog.