Bug 514442 – crash in Home Folder: retry

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 514442 - crash in Home Folder: retry


Summary:	crash in Home Folder: retry


Status:	RESOLVED DUPLICATE of bug 459221

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-05 01:04 UTC by xiangyzhang
Modified:	2008-02-05 10:12 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description xiangyzhang 2008-02-05 01:04:31 UTC

What were you doing when the application crashed?
retry


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.2 2007-11-27 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-2952.fc8xen #1 SMP Mon Nov 19 07:06:36 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 564555776 vsize: 564555776 resident: 36126720 share: 20250624 rss: 36126720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202173359 rtime: 128 utime: 118 stime: 10 cutime:34 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496423168 (LWP 3555)]
(no debugging symbols found)
0x000000354300d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 188116

Thread 1 (Thread 46912496423168 (LWP 3555))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 g_assert_warning
from /lib64/libglib-2.0.so.0
#8 ??
#9 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#10 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit
from /lib64/libgobject-2.0.so.0
#13 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#15 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit
from /lib64/libgobject-2.0.so.0
#18 gtk_tree_model_row_deleted
from /usr/lib64/libgtk-x11-2.0.so.0
#19 gtk_list_store_remove
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_list_store_clear
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
#22 ??
#23 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#24 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#25 g_main_loop_run
from /lib64/libglib-2.0.so.0
#26 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#27 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
--- Hash table keys for warning below:
--> file:///root
(nautilus:3529): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
--- Hash table keys for warning below:
--> file:///root
(nautilus:3566): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-02-05 10:12:36 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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