Bug 496988 – crash in Open Folder: changing directory in na...

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 496988 - crash in Open Folder: changing directory in na...


Summary:	crash in Open Folder: changing directory in na...


Status:	RESOLVED DUPLICATE of bug 479586

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-11-15 08:54 UTC by David Abbott
Modified:	2007-11-15 15:01 UTC

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

Description David Abbott 2007-11-15 08:54:25 UTC

Version: 2.18.3

What were you doing when the application crashed?
changing directory in nautilus


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-11-04 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r9 #1 SMP Sat Nov 3 23:02:56 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Neu

Memory status: size: 372768768 vsize: 372768768 resident: 33460224 share: 20357120 rss: 33460224 rss_rlim: 18446744073709551615
CPU usage: start_time: 1195114342 rtime: 152 utime: 139 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00002b69273e4a0f in waitpid () from /lib/libpthread.so.0

+ Trace 177827

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

Comment 1 palfrey 2007-11-15 15:01:59 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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