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 157551 - Error: The Application "nautilus-cd-burner" has quit unexpectedly.
Error: The Application "nautilus-cd-burner" has quit unexpectedly.
Status: RESOLVED DUPLICATE of bug 157387
Product: nautilus-cd-burner
Classification: Deprecated
Component: burn vfs-method
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-07 00:50 UTC by skiffworks
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description skiffworks 2004-11-07 00:51:11 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 ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_combo_box_get_active
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 bacon_cd_selection_set_recorders_only
    at bacon-cd-selection.c line 332
  • #6 bacon_cd_selection_set_property
    at bacon-cd-selection.c line 388
  • #7 g_object_set_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #9 target_optionmenu_create
    at nautilus-cd-burner.c line 839
  • #10 glade_xml_ensure_accel
    from /usr/lib/libglade-2.0.so.0
  • #11 glade_set_custom_handler
    from /usr/lib/libglade-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /usr/lib/libglade-2.0.so.0
  • #21 ??
  • #22 glade_set_custom_handler
    from /usr/lib/libglade-2.0.so.0
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 gtk_widget_get_type
    from /usr/lib/libgtk-x11-2.0.so.0




------- 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.

Comment 1 Sebastien Bacher 2004-11-07 21:45:07 UTC
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 ***