Bug 479542 – crash in File Browser: I've just opened a folde...

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 479542 - crash in File Browser: I've just opened a folde...


Summary:	crash in File Browser: I've just opened a folde...


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-23 14:59 UTC by Jakub 'Livio' Rusinek
Modified:	2007-09-25 10:52 UTC

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

Description Jakub 'Livio' Rusinek 2007-09-23 14:59:00 UTC

Version: 2.18.3

What were you doing when the application crashed?
I've just opened a folder from another (browser mode).
I have nautilus-debuginfo and gtk2-debuginfo.


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Livious

Memory status: size: 93700096 vsize: 93700096 resident: 20766720 share: 14266368 rss: 20766720 rss_rlim: 4294967295
CPU usage: start_time: 1190557321 rtime: 1034 utime: 898 stime: 136 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 -1208969504 (LWP 10036)]
0x00110402 in __kernel_vsyscall ()

+ Trace 164853

Thread 1 (Thread -1208969504 (LWP 10036))

#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 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 view_as_menu_switch_views_callback
at nautilus-navigation-window.c line 834
#11 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /lib/libgobject-2.0.so.0
#19 ??
from /lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#21 g_signal_emit
from /lib/libgobject-2.0.so.0
#22 gtk_tree_model_row_deleted
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_list_store_remove
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_list_store_clear
from /usr/lib/libgtk-x11-2.0.so.0
#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 ??
from /lib/libglib-2.0.so.0
#29 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#30 ??
from /lib/libglib-2.0.so.0
#31 g_main_loop_run
from /lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main
at nautilus-main.c line 548
#0 __kernel_vsyscall

Comment 1 Mart Raudsepp 2007-09-25 10:52:42 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 ***