GNOME Bugzilla – Bug 157551
Error: The Application "nautilus-cd-burner" has quit unexpectedly.
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: nautilus-cd-burner Severity: normal Version: GNOME2.8.1 unspecified Gnome-Distributor: Ubuntu Synopsis: Error: The Application "nautilus-cd-burner" has quit unexpectedly. Bugzilla-Product: nautilus-cd-burner Bugzilla-Component: burn vfs-method Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: In Hoary Warthog, try to burn an .iso file with 'nautilus-cd-burner' and get the following Error: "The Application "nautilus-cd-burner" has quit unexpectedly. You can inform the developers of what happened to help them fix it. Or you can restart the application right now." Steps to reproduce the crash: 1. Right click on .iso file. 2. Click on "Write to disk..." 3. Error box pops up. Expected Results: Error message box; "The Application "nautilus-cd-burner" has quit unexpectedly." How often does this happen? Everytime. Additional Information: Prior to the most recent Hoary update(Saturday morning, 11-06), I was successful burning over a dozen .iso files, tried three different .iso files. Debugging Information: Backtrace was generated from '/usr/bin/nautilus-cd-burner' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1089385088 (LWP 6128)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 51696
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-06 19:51 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus-cd-burner". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was skiffworks@earthlink.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 157387 ***