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 368579 - crash in CD/DVD Creator: Starting X
crash in CD/DVD Creator: Starting X
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-10-31 22:13 UTC by alan.mclaughlin
Modified: 2006-11-01 18:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description alan.mclaughlin 2006-10-31 22:13:25 UTC 
What were you doing when the application crashed?
Starting X


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: 120582144 vsize: 0 resident: 120582144 share: 0 rss: 20611072 rss_rlim: 0
CPU usage: start_time: 1162332725 rtime: 0 utime: 118 stime: 0 cutime:98 cstime: 0 timeout: 20 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 -1208136960 (LWP 3803)]
(no debugging symbols found)
0x0046b402 in __kernel_vsyscall ()

+ Trace 81195

Thread 1 (Thread -1208136960 (LWP 3803))

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






Comment 1


Behdad Esfahbod





          2006-10-31 22:19:43 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 367701 ***






Comment 2


Behdad Esfahbod





          2006-11-01 18:09:07 UTC
        




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