Bug 507180 – crash in Home 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 507180 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 440988

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-04 04:32 UTC by slaidel
Modified:	2008-01-05 18:47 UTC

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

Description slaidel 2008-01-04 04:32:35 UTC

What were you doing when the application crashed?



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

System: Linux 2.6.22-3-686-bigmem #1 SMP Mon Nov 12 09:52:20 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: mac-osx-controls
Icon Theme: OSX

Memory status: size: 92880896 vsize: 92880896 resident: 33144832 share: 16629760 rss: 33144832 rss_rlim: 4294967295
CPU usage: start_time: 1199411335 rtime: 1918 utime: 1791 stime: 127 cutime:0 cstime: 2 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6de96b0 (LWP 5827)]
(no debugging symbols found)
0xb763e321 in waitpid () from /lib/libpthread.so.0

+ Trace 184007

Thread 1 (Thread 0xb6de96b0 (LWP 5827))

#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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
from /usr/lib/libgtk-x11-2.0.so.0
#48 ??
#49 ??
#50 ??
#51 ??
#52 ??
#53 ??
#54 g_sequence_sort_changed_iter
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
kdevelop (core): [virtual void DDockWindow::addWidget(const QString&, QWidget*, bool)] 
kdevelop (core): [virtual void DDockWindow::addWidget(const QString&, QWidget*, bool)] 
kio_http_cache_cleaner: Already running! (kio_http_cache_cleaner-2)
kdevelop (core): caption change
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
kdevelop (core): [void DDockWindow::selectWidget(Ideal::Button*)] 
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 2008-01-05 18:47:29 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 ***