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 119106 - Nautilus crashed when I hit ^N to open a new window
Nautilus crashed when I hit ^N to open a new window
Status: RESOLVED DUPLICATE of bug 111147
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-08-04 17:16 UTC by reast
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description reast 2003-08-04 17:16:24 UTC 
Package: nautilus
Severity: normal
Version: 2.2.1
Synopsis: Nautilus crashed when I hit ^N to open a new window
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
This seems to happen intermittently, and not always when ^N is typed

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:
Instead of new window appearing, BugBuddy appears
Usually afetr the crash, Nautilus restarts and behaves better

Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1088008512 (LWP 5648)]
[New Thread 1167306032 (LWP 5680)]
[New Thread 1158913328 (LWP 5679)]
[New Thread 1150520624 (LWP 5678)]
[New Thread 1142127920 (LWP 5677)]
[New Thread 1133735216 (LWP 5663)]
[New Thread 1125342512 (LWP 5659)]
[New Thread 1116949808 (LWP 5654)]
[New Thread 1099619632 (LWP 5653)]
0xffffe002 in ??
    ()

+ Trace 39330

Thread 1 (Thread 1088008512 (LWP 5648))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 FAMClose
    from /usr/lib/libfam.so.0
  • #4 FAMMonitorDirectory
    from /usr/lib/libfam.so.0
  • #5 _init
    from /usr/lib/gnome-vfs-2.0/modules/libfile.so
  • #6 _gnome_vfs_monitor_do_add
    from /usr/lib/libgnomevfs-2.so.0
  • #7 gnome_vfs_monitor_add
    from /usr/lib/libgnomevfs-2.so.0
  • #8 nautilus_monitor_active
    from /usr/lib/libnautilus-private.so.2
  • #9 nautilus_monitor_directory
    from /usr/lib/libnautilus-private.so.2
  • #10 nautilus_directory_monitor_add_internal
    from /usr/lib/libnautilus-private.so.2
  • #11 nautilus_vfs_directory_get_type
    from /usr/lib/libnautilus-private.so.2
  • #12 nautilus_directory_file_monitor_add
    from /usr/lib/libnautilus-private.so.2
  • #13 fm_directory_view_activate_files
  • #14 nautilus_directory_add_file_monitors
    from /usr/lib/libnautilus-private.so.2
  • #15 nautilus_async_destroying_file
    from /usr/lib/libnautilus-private.so.2
  • #16 nautilus_directory_async_state_changed
    from /usr/lib/libnautilus-private.so.2
  • #17 nautilus_directory_call_when_ready_internal
    from /usr/lib/libnautilus-private.so.2
  • #18 nautilus_vfs_directory_get_type
    from /usr/lib/libnautilus-private.so.2
  • #19 nautilus_directory_call_when_ready
    from /usr/lib/libnautilus-private.so.2
  • #20 fm_directory_view_activate_files
  • #21 fm_directory_view_send_selection_change
  • #22 g_cclosure_marshal_VOID__STRING
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #27 nautilus_uri_list_from_g_list
    from /usr/lib/libnautilus.so.2
  • #28 nautilus_clipboard_set_up_editable_in_control
    from /usr/lib/libnautilus.so.2
  • #29 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #30 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #34 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 main
  • #36 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-04 13:16 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-08-04 17:24:38 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 111147 ***