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 368654 - crash in CD/DVD Creator: I attempted to open my h...
crash in CD/DVD Creator: I attempted to open my h...
Status: RESOLVED DUPLICATE of bug 351713
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-01 01:50 UTC by casper911ca
Modified: 2006-11-01 09:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description casper911ca 2006-11-01 01:50:57 UTC 
What were you doing when the application crashed?
I attempted to open my home folder and it proceeded to open ten instead. This screen popped telling me it crashed.


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

Memory status: size: 77975552 vsize: 0 resident: 77975552 share: 0 rss: 16396288 rss_rlim: 0
CPU usage: start_time: 1162302000 rtime: 0 utime: 60 stime: 0 cutime:58 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

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

+ Trace 81258

Thread 1 (Thread -1208169728 (LWP 4100))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/libc.so.6
  • #5 g_strdup
    from /lib/libglib-2.0.so.0
  • #6 nautilus_directory_async_state_changed
  • #7 nautilus_file_get_uri
  • #8 nautilus_file_get_uri
  • #9 nautilus_file_has_volume
  • #10 nautilus_icon_container_request_update_all
  • #11 fm_directory_view_bump_zoom_level
  • #12 nautilus_file_ref
  • #13 nautilus_icon_container_request_update_all
  • #14 fm_directory_view_bump_zoom_level
  • #15 fm_directory_view_supports_zooming
  • #16 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 nautilus_file_get_uri
  • #22 nautilus_file_get_uri
  • #23 nautilus_undo_transaction_unregister_object
  • #24 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #29 nautilus_file_get_uri
  • #30 nautilus_directory_async_state_changed
  • #31 nautilus_directory_async_state_changed
  • #32 nautilus_undo_transaction_unregister_object
  • #33 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #34 g_cclosure_marshal_VOID__ENUM
  • #35 nautilus_marshal_BOOLEAN__POINTER
  • #36 nautilus_marshal_BOOLEAN__POINTER
  • #37 eel_read_file_cancel
    from /usr/lib/libeel-2.so.2
  • #38 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #39 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #40 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #41 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #42 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #43 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #44 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 POA_Nautilus_MetafileMonitor__init
  • #46 __libc_start_main
    from /lib/libc.so.6
  • #47 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-11-01 09:18:46 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 351713 ***