Bug 478030 – crash in Open Folder:

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 478030 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 459221

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-18 13:07 UTC by Víctor Daniel
Modified:	2007-09-18 19:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Víctor Daniel 2007-09-18 13:07:03 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Raleigh
Icon Theme: gnome

Memory status: size: 78008320 vsize: 78008320 resident: 17965056 share: 13541376 rss: 17965056 rss_rlim: 4294967295
CPU usage: start_time: 1190121087 rtime: 223 utime: 177 stime: 46 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208908064 (LWP 14571)]
0x0012d402 in __kernel_vsyscall ()

+ Trace 163745

Thread 1 (Thread -1208908064 (LWP 14571))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 *__GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#6 *__GI_abort
at abort.c line 88
#7 IA__g_logv
#8 IA__g_log
#9 IA__g_assert_warning
#10 view_as_menu_switch_views_callback
at nautilus-navigation-window.c line 834
#11 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#12 IA__g_closure_invoke
at gclosure.c line 490
#13 signal_emit_unlocked_R
at gsignal.c line 2440
#14 IA__g_signal_emit_valist
at gsignal.c line 2199
#15 IA__g_signal_emit
at gsignal.c line 2243
#16 gtk_combo_box_model_row_deleted
at gtkcombobox.c line 3119
#17 IA__g_cclosure_marshal_VOID__BOXED
at gmarshal.c line 566
#18 IA__g_closure_invoke
at gclosure.c line 490
#19 signal_emit_unlocked_R
at gsignal.c line 2440
#20 IA__g_signal_emit_valist
at gsignal.c line 2199
#21 IA__g_signal_emit
at gsignal.c line 2243
#22 IA__gtk_tree_model_row_deleted
at gtktreemodel.c line 1537
#23 IA__gtk_list_store_remove
at gtkliststore.c line 969
#24 IA__gtk_list_store_clear
at gtkliststore.c line 1167
#25 load_view_as_menu
at nautilus-navigation-window.c line 884
#26 ready_callback_call
at nautilus-directory-async.c line 1265
#27 call_ready_callbacks_at_idle
at nautilus-directory-async.c line 1883
#28 g_idle_dispatch
at gmain.c line 4132
#29 IA__g_main_context_dispatch
at gmain.c line 2061
#30 g_main_context_iterate
at gmain.c line 2694
#31 IA__g_main_loop_run
at gmain.c line 2898
#32 IA__gtk_main
at gtkmain.c line 1144
#33 main
at nautilus-main.c line 548
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
localuser:vdmo being added to access control list
SESSION_MANAGER=local/unknown-00-0e-a6-1c-ea-84.lan:/tmp/.ICE-unix/14285
--- Hash table keys for warning below:
--> file:///home/vdmo
(nautilus:14402): 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...
Cannot access memory at address 0x38eb
Cannot access memory at address 0x38eb
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-09-18 19:31:53 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 ***