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 108313 - Nautilus crashes (text view?)
Nautilus crashes (text view?)
Status: RESOLVED DUPLICATE of bug 119407
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-03-13 15:59 UTC by mithrir
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description mithrir 2003-03-13 15:58:42 UTC 
Package: nautilus
Severity: critical
Version: GNOME2.2.0 2.2.2
os_details: Gnome.Org
Synopsis: Nautilus crashes (text view?)
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:


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

Actual Results:


Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/home/gar/garnome/bin/nautilus'

[New Thread 8192 (LWP 28247)]
[New Thread 16385 (LWP 28253)]
[New Thread 8194 (LWP 28254)]
[New Thread 16387 (LWP 28255)]
[New Thread 24580 (LWP 28256)]
[New Thread 32773 (LWP 28257)]
[New Thread 40966 (LWP 28258)]
[New Thread 49159 (LWP 28259)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 34855

Thread 8 (Thread 49159 (LWP 28259))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    at gnome-vfs-thread-pool.c line 158
  • #4 thread_entry
    at gnome-vfs-thread-pool.c line 172
  • #5 g_thread_create_proxy
    at gthread.c line 551
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 7 (Thread 40966 (LWP 28258))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    at gnome-vfs-thread-pool.c line 158
  • #4 thread_entry
    at gnome-vfs-thread-pool.c line 172
  • #5 g_thread_create_proxy
    at gthread.c line 551
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 6 (Thread 32773 (LWP 28257))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    at gnome-vfs-thread-pool.c line 158
  • #4 thread_entry
    at gnome-vfs-thread-pool.c line 172
  • #5 g_thread_create_proxy
    at gthread.c line 551
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 5 (Thread 24580 (LWP 28256))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    at gnome-vfs-thread-pool.c line 158
  • #4 thread_entry
    at gnome-vfs-thread-pool.c line 172
  • #5 g_thread_create_proxy
    at gthread.c line 551
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 4 (Thread 16387 (LWP 28255))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    at gnome-vfs-thread-pool.c line 158
  • #4 thread_entry
    at gnome-vfs-thread-pool.c line 172
  • #5 g_thread_create_proxy
    at gthread.c line 551
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 3 (Thread 8194 (LWP 28254))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    at gnome-vfs-thread-pool.c line 158
  • #4 thread_entry
    at gnome-vfs-thread-pool.c line 172
  • #5 g_thread_create_proxy
    at gthread.c line 551
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #8 nautilus_window_back_or_forward
    at nautilus-window-manage-views.c line 2253
  • #9 nautilus_window_go_back
    at nautilus-window.c line 1583
  • #10 marshal_VOID__USER_DATA_STRING
    at bonobo-ui-component.c line 221
  • #11 g_closure_invoke
    at gclosure.c line 437
  • #12 bonobo_closure_invoke_va_list
    at bonobo-types.c line 415
  • #13 bonobo_closure_invoke
    at bonobo-types.c line 474
  • #19 g_type_class_meta_marshal
    at gclosure.c line 514
  • #20 g_closure_invoke
    at gclosure.c line 437
  • #21 signal_emit_unlocked_R
    at gsignal.c line 2860
  • #23 g_signal_emit
    at gsignal.c line 2612
  • #24 bonobo_ui_engine_emit_verb_on_w
    at bonobo-ui-engine.c line 3015
  • #25 exec_verb_cb
    at bonobo-ui-sync-toolbar.c line 191
  • #26 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #27 g_closure_invoke
    at gclosure.c line 437
  • #28 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #29 g_signal_emit_valist
    at gsignal.c line 2554
  • #30 g_signal_emit
    at gsignal.c line 2612
  • #31 bonobo_ui_toolbar_item_activate
    at bonobo-ui-toolbar-item.c line 447
  • #32 button_widget_clicked_cb
    at bonobo-ui-toolbar-button-item.c line 217
  • #33 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #34 g_closure_invoke
    at gclosure.c line 437
  • #35 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #36 g_signal_emit_valist
    at gsignal.c line 2554
  • #37 g_signal_emit
    at gsignal.c line 2612
  • #38 gtk_button_clicked
    at gtkbutton.c line 555
  • #39 gtk_real_button_released
    at gtkbutton.c line 1044
  • #40 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #41 g_type_class_meta_marshal
    at gclosure.c line 514
  • #42 g_closure_invoke
    at gclosure.c line 437
  • #43 signal_emit_unlocked_R
    at gsignal.c line 2752
  • #44 g_signal_emit_valist
    at gsignal.c line 2554
  • #45 g_signal_emit
    at gsignal.c line 2612
  • #46 gtk_button_released
    at gtkbutton.c line 547
  • #47 gtk_button_button_release
    at gtkbutton.c line 960
  • #48 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #49 g_type_class_meta_marshal
    at gclosure.c line 514
  • #50 g_closure_invoke
    at gclosure.c line 437
  • #51 signal_emit_unlocked_R
    at gsignal.c line 2860
  • #53 g_signal_emit
    at gsignal.c line 2612
  • #54 gtk_widget_event_internal
    at gtkwidget.c line 3143
  • #55 gtk_propagate_event
    at gtkmain.c line 2267
  • #56 gtk_main_do_event
    at gtkmain.c line 1502
  • #57 gdk_event_dispatch
    at gdkevents-x11.c line 2018
  • #58 g_main_dispatch
    at gmain.c line 1653
  • #59 g_main_context_dispatch
    at gmain.c line 2197
  • #60 g_main_context_iterate
    at gmain.c line 2278
  • #61 g_main_loop_run
    at gmain.c line 2498
  • #62 gtk_main
    at gtkmain.c line 1092
  • #63 main
    at nautilus-main.c line 267
  • #64 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-13 10:58 -------

The original reporter (mithrir@yahoo.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-03-13 22:04:08 UTC 
Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.2.x; adding GNOMEVER2.2,
STACKTRACE (due to the symbols), and bugsquad keywords; and marking as
new.
Comment 2 Alexander Larsson 2003-03-14 10:52:12 UTC 
I don't understand this bug? It seems to be when you "go back" from
viewing a text file to the directory. Looking at the backtrace it
seems view->details is NULL. But that sounds really weird.

Can you reproduce this?
Comment 3 Elijah Newren 2003-08-26 15:13:14 UTC 
I believe that bug 116651 is a duplicate of this bug as the stack
traces are a pretty close, though not perfect, match.
Comment 4 Alexander Larsson 2003-09-18 13:01:08 UTC 
I don't think so,  bug 116651 looks different, while this is a dup of
bug 117931

*** This bug has been marked as a duplicate of 117931 ***
Comment 5 Alexander Larsson 2003-09-18 13:05:14 UTC 
sorry, i mean 119407
Comment 6 Alexander Larsson 2003-09-18 13:05:40 UTC 

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