Bug 493963 – crash in File Browser:

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 493963 - crash in File Browser:


Summary:	crash in File Browser:


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:	2007-11-06 00:03 UTC by sjermakowicz
Modified:	2007-11-06 12:12 UTC

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

Description sjermakowicz 2007-11-06 00:03:11 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 75206656 vsize: 75206656 resident: 25853952 share: 15089664 rss: 25853952 rss_rlim: 4294967295
CPU usage: start_time: 1194293612 rtime: 496 utime: 456 stime: 40 cutime:52 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e496b0 (LWP 5445)]
[New Thread 0xb6572b90 (LWP 14008)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 175582

Thread 1 (Thread 0xb6e496b0 (LWP 5445))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/i686/cmov/libc.so.6
#6 abort
from /lib/i686/cmov/libc.so.6
#7 IA__g_logv
#8 IA__g_log
#9 IA__g_assert_warning
#10 gtk_list_store_compare_func
at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1677
#11 node_find_closest
at gsequence.c line 1136
#12 node_insert_sorted
at gsequence.c line 1301
#13 g_sequence_sort_changed_iter
at gsequence.c line 566
#14 gtk_list_store_sort_iter_changed
at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1758
#15 IA__gtk_list_store_set_valist
at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 901
#16 IA__gtk_list_store_set
at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 934
#17 ??
from /usr/lib/libeel-2-2.18.so
#18 ??
#19 ??
#20 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Gtk-ERROR **: file /tmp/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...
--------------------------------------------------

Comment 1 André Klapper 2007-11-06 12:12:28 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 440988 ***