Bug 510037 – crash in Open Folder: Attempting to enter an a...

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 510037 - crash in Open Folder: Attempting to enter an a...


Summary:	crash in Open Folder: Attempting to enter an a...


Status:	RESOLVED DUPLICATE of bug 440988

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:	2008-01-17 00:30 UTC by Paul Barbee
Modified:	2008-01-17 01:11 UTC

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

Description Paul Barbee 2008-01-17 00:30:46 UTC

Version: 2.18.3

What were you doing when the application crashed?
Attempting to enter an address in Nautilus


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 389120000 vsize: 389120000 resident: 31186944 share: 17723392 rss: 31186944 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200529799 rtime: 216 utime: 196 stime: 20 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)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b4d6f109540 (LWP 5880)]
(no debugging symbols found)
0x00002b4d6859234f in waitpid () from /lib/libpthread.so.0

+ Trace 185632

Thread 1 (Thread 0x2b4d6f109540 (LWP 5880))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
#12 ??
#13 g_sequence_sort_iter
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#21 ??
from /usr/lib/libgnomevfs-2.so.0
#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_dialog_run
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 ??
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#33 ??
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#35 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgtk-x11-2.0.so.0
#38 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#39 ??
from /usr/lib/libgobject-2.0.so.0
#40 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#41 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgdk-x11-2.0.so.0
#46 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#47 ??
from /usr/lib/libglib-2.0.so.0
#48 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#49 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#50 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(PySwitcher.py:4085): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
(PySwitcher.py:4085): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
Gtk-ERROR **: file /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
(PySwitcher.py:4085): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
--------------------------------------------------

Comment 1 André Klapper 2008-01-17 01:11:01 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 440988 ***