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 424945 - crash in CD/DVD Creator:
crash in CD/DVD Creator:
Status: RESOLVED DUPLICATE of bug 363289
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-31 17:56 UTC by peter.s
Modified: 2007-04-01 22:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description peter.s 2007-03-31 17:56:13 UTC
What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 96485376 vsize: 0 resident: 96485376 share: 0 rss: 22388736 rss_rlim: 0
CPU usage: start_time: 1175363732 rtime: 0 utime: 126 stime: 0 cutime:112 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226574160 (LWP 9765)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226574160 (LWP 9765))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_insert
    from /usr/lib/libglib-2.0.so.0
  • #6 _gtk_icon_cache_add_icons
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_icon_theme_list_icons
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 nautilus_directory_ref
  • #9 POA_Nautilus_MetafileMonitor__init
  • #10 POA_Nautilus_MetafileMonitor__init
  • #11 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #16 POA_Nautilus_MetafileMonitor__init
  • #17 nautilus_marshal_BOOLEAN__POINTER
  • #18 POA_Nautilus_MetafileMonitor__init
  • #19 POA_Nautilus_MetafileMonitor__init
  • #20 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 gtk_widget_show
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 POA_Nautilus_MetafileMonitor__init
  • #28 nautilus_undo_transaction_unregister_object
  • #29 fm_directory_view_bump_zoom_level
  • #30 nautilus_clipboard_monitor_emit_changed
  • #31 nautilus_directory_async_state_changed
  • #32 nautilus_icon_container_request_update_all
  • #33 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #35 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #37 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 POA_Nautilus_MetafileMonitor__init
  • #39 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #40 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2007-04-01 22:47:28 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 363289 ***