Bug 130892 – Problems with browsing Nautilus

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 130892 - Problems with browsing Nautilus


Summary:	Problems with browsing Nautilus


Status:	RESOLVED DUPLICATE of bug 91588

Product:	nautilus
Classification:	Core
Component:	Navigation
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-01-08 14:30 UTC by jairoconceicao
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description jairoconceicao 2004-01-08 14:26:36 UTC

Package: nautilus
Severity: normal
Version: 2.0.6
Synopsis: Problems with browsing Nautilus
Bugzilla-Product: nautilus
Bugzilla-Component: Navigation
BugBuddy-GnomeVersion: 2.0 (2.0.3)

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 '/usr/bin/nautilus'

(no debugging symbols found)...[New Thread 8192 (LWP 4546)]
[New Thread 16385 (LWP 4547)]
[New Thread 8194 (LWP 4548)]
[New Thread 16387 (LWP 4549)]
[New Thread 24580 (LWP 4608)]
[New Thread 32773 (LWP 4609)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 43084

Thread 1 (Thread 8192 (LWP 4546))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 kill
from /lib/i686/libc.so.6
#7 raise
from /lib/i686/libpthread.so.0
#8 abort
from /lib/i686/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 nautilus_tree_model_unref_node
at nautilus-tree-model.c line 1357
#12 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_model_sort_real_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_tree_model_sort_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_tree_view_unref_tree_helper
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_tree_view_unref_and_check_selection_tree
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_tree_view_real_collapse_row
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_tree_view_button_release
from /usr/lib/libgtk-x11-2.0.so.0
#20 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#30 g_main_dispatch
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_iterate
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/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-01-08 09:26 -------

The original reporter (jairoconceicao@bol.com.br) 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 Alex Duggan 2004-01-08 15:19:01 UTC


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