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 390880 - crash in CD/DVD Creator: Changing from one dir to...
crash in CD/DVD Creator: Changing from one dir to...
Status: RESOLVED DUPLICATE of bug 360543
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-30 05:11 UTC by bdminton
Modified: 2006-12-30 10:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description bdminton 2006-12-30 05:11:51 UTC
What were you doing when the application crashed?
Changing from one dir to another in my /home/dir


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

Memory status: size: 79126528 vsize: 0 resident: 79126528 share: 0 rss: 20819968 rss_rlim: 0
CPU usage: start_time: 1167449465 rtime: 0 utime: 1644 stime: 0 cutime:1486 cstime: 0 timeout: 158 it_real_value: 0 frequency: 240

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 -1226819920 (LWP 4395)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226819920 (LWP 4395))

  • #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 nautilus_clipboard_monitor_emit_changed
  • #5 nautilus_clipboard_monitor_emit_changed
  • #6 nautilus_directory_async_state_changed
  • #7 nautilus_directory_async_state_changed
  • #8 nautilus_undo_transaction_unregister_object
  • #9 nautilus_file_get_uri
  • #10 POA_Nautilus_MetafileMonitor__init
  • #11 POA_Nautilus_MetafileMonitor__init
  • #12 g_cclosure_marshal_VOID__STRING
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #17 POA_Nautilus_MetafileMonitor__init
  • #18 nautilus_undo_transaction_unregister_object
  • #19 fm_directory_view_bump_zoom_level
  • #20 nautilus_clipboard_monitor_emit_changed
  • #21 nautilus_directory_async_state_changed
  • #22 nautilus_icon_container_request_update_all
  • #23 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 POA_Nautilus_MetafileMonitor__init
  • #29 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #30 ??
  • #0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-12-30 10:41:50 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 360543 ***