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 449979 - crash in CD/DVD Creator: Opened nautilus in brows...
crash in CD/DVD Creator: Opened nautilus in brows...
Status: RESOLVED DUPLICATE of bug 363856
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-22 07:49 UTC by THESEMEY
Modified: 2007-06-22 22:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description THESEMEY 2007-06-22 07:49:11 UTC 
What were you doing when the application crashed?
Opened nautilus in browser mode, used Go-Search for files (Ctrl+F) and entered "htm" as search string.
This error is reproducible.


Distribution: Red Hat Enterprise Linux Client release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 128233472 vsize: 0 resident: 128233472 share: 0 rss: 33681408 rss_rlim: 0
CPU usage: start_time: 1182498287 rtime: 0 utime: 356 stime: 0 cutime:318 cstime: 0 timeout: 38 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 -1208505600 (LWP 5317)]
(no debugging symbols found)
0x00596410 in __kernel_vsyscall ()

+ Trace 142832

Thread 1 (Thread -1208505600 (LWP 5317))

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






Comment 1


André Klapper





          2007-06-22 22:35:58 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 363856 ***