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 369080 - crash in CD/DVD Creator: I changed the Properties...
crash in CD/DVD Creator: I changed the Properties...
Status: RESOLVED DUPLICATE of bug 355216
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-01 21:33 UTC by jon
Modified: 2006-11-01 22:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description jon 2006-11-01 21:33:11 UTC
What were you doing when the application crashed?
I changed the Properties to Allow the Delete button on the menus to bypass the trash can while viewing Dir / in File Browser and Clicked Reload button -- once i clicked Reload it Errored out -- I am also downloading Updates from synaptic at the same time


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

Memory status: size: 90300416 vsize: 0 resident: 90300416 share: 0 rss: 29356032 rss_rlim: 0
CPU usage: start_time: 1162352502 rtime: 0 utime: 2323 stime: 0 cutime:2136 cstime: 0 timeout: 187 it_real_value: 0 frequency: 114

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

Thread 1 (Thread -1226971472 (LWP 4622))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 fm_directory_view_bump_zoom_level
  • #11 nautilus_file_ref
  • #12 nautilus_icon_container_request_update_all
  • #13 fm_directory_view_bump_zoom_level
  • #14 fm_directory_view_supports_zooming
  • #15 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 nautilus_file_get_uri
  • #21 nautilus_file_get_uri
  • #22 nautilus_directory_async_state_changed
  • #23 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
    from /usr/lib/libgthread-2.0.so.0
  • #28 ??
  • #29 ??
    from /usr/lib/libglib-2.0.so.0
  • #30 ??
  • #31 g_slice_alloc
    from /usr/lib/libglib-2.0.so.0
  • #32 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #36 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 POA_Nautilus_MetafileMonitor__init
  • #38 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #39 ??
  • #0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-11-01 22:18:25 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 355216 ***