Bug 510489 – crash in Open Folder: I went into properties t...

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 510489 - crash in Open Folder: I went into properties t...


Summary:	crash in Open Folder: I went into properties t...


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-18 21:25 UTC by erik
Modified:	2008-01-19 01:22 UTC

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

Description erik 2008-01-18 21:25:39 UTC

Version: 2.18.3

What were you doing when the application crashed?
I went into properties to change the "open with" application.  I changed the "open with" property.  Then the icons on the desktop and the nautilus windows disappeared.

Now, when I right click on a file and select "properties" I get this error.



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

System: Linux 2.6.22 #1 SMP Wed Nov 14 17:40:02 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: NoiaWarm

Memory status: size: 401862656 vsize: 401862656 resident: 29261824 share: 16109568 rss: 29261824 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200691247 rtime: 116 utime: 103 stime: 13 cutime:2 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 0x2b8134f0e540 (LWP 7642)]
0x00002b812e39734f in waitpid () from /lib/libpthread.so.0

+ Trace 185881

Thread 1 (Thread 0x2b8134f0e540 (LWP 7642))

#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 gtk_list_store_compare_func
at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1677
#11 ??
#12 ??
#13 g_sequence_sort_changed_iter
#14 gtk_list_store_sort_iter_changed
at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1758
#15 IA__gtk_list_store_set_valist
at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 901
#16 IA__gtk_list_store_set
at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 934
#17 ??
from /usr/lib/libeel-2-2.18.so
#18 eel_mime_application_chooser_new
from /usr/lib/libeel-2-2.18.so
#19 ??
#20 ??
#21 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#22 ??
from /usr/lib/libglib-2.0.so.0
#23 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#24 IA__gtk_main
at /build/buildd/gtk+2.0-2.12.1/gtk/gtkmain.c line 1146
#25 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
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
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...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-19 01:22:54 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 ***