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 384098 - crash in CD/DVD Creator:
crash in CD/DVD Creator:
Status: RESOLVED DUPLICATE of bug 377558
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-09 16:56 UTC by rruhland
Modified: 2006-12-10 13:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rruhland 2006-12-09 16:56:02 UTC 
What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.1 2006-10-07 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 88322048 vsize: 0 resident: 88322048 share: 0 rss: 26230784 rss_rlim: 0
CPU usage: start_time: 1165652032 rtime: 0 utime: 27486 stime: 0 cutime:22778 cstime: 0 timeout: 4708 it_real_value: 0 frequency: 15894

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209215296 (LWP 3234)]
0x00f87402 in __kernel_vsyscall ()

+ Trace 92831

Thread 1 (Thread -1209215296 (LWP 3234))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 lacks_info
  • #5 file_needs_high_priority_work_done
  • #6 nautilus_directory_async_state_changed
  • #7 call_ready_callbacks_at_idle
  • #8 g_idle_dispatch
    at gmain.c line 3924
  • #9 g_main_context_dispatch
    at gmain.c line 2043
  • #10 g_main_context_iterate
    at gmain.c line 2675
  • #11 g_main_loop_run
    at gmain.c line 2879
  • #12 location_button_clicked_callback
  • #13 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #14 g_closure_invoke
    at gclosure.c line 490
  • #15 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #16 g_signal_emit_valist
    at gsignal.c line 2197
  • #17 g_signal_emit
    at gsignal.c line 2241
  • #18 gtk_button_clicked
    at gtkbutton.c line 889
  • #19 gtk_real_button_released
    at gtkbutton.c line 1484
  • #20 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #21 g_type_class_meta_marshal
    at gclosure.c line 567
  • #22 g_closure_invoke
    at gclosure.c line 490
  • #23 signal_emit_unlocked_R
    at gsignal.c line 2368
  • #24 g_signal_emit_valist
    at gsignal.c line 2197
  • #25 g_signal_emit
    at gsignal.c line 2241
  • #26 gtk_button_released
    at gtkbutton.c line 881
  • #27 gtk_button_button_release
    at gtkbutton.c line 1377
  • #28 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #29 g_type_class_meta_marshal
    at gclosure.c line 567
  • #30 g_closure_invoke
    at gclosure.c line 490
  • #31 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #32 g_signal_emit_valist
    at gsignal.c line 2207
  • #33 g_signal_emit
    at gsignal.c line 2241
  • #34 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #35 gtk_propagate_event
    at gtkmain.c line 2188
  • #36 gtk_main_do_event
    at gtkmain.c line 1422
  • #37 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #38 g_main_context_dispatch
    at gmain.c line 2043
  • #39 g_main_context_iterate
    at gmain.c line 2675
  • #40 g_main_loop_run
    at gmain.c line 2879
  • #41 gtk_main
    at gtkmain.c line 1001
  • #42 main
  • #0 __kernel_vsyscall 






Comment 1


Rob Bradford





          2006-12-10 13:34:00 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 377558 ***