Bug 481476 – crash in Open Folder: I was opening the proper...

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 481476 - crash in Open Folder: I was opening the proper...


Summary:	crash in Open Folder: I was opening the proper...


Status:	RESOLVED DUPLICATE of bug 479483

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-09-29 01:08 UTC by gordonbrown
Modified:	2007-10-03 11:09 UTC

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

Description gordonbrown 2007-09-29 01:08:52 UTC

Version: 2.18.3

What were you doing when the application crashed?
I was opening the properties dialogue of a movie file.


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

System: Linux 2.6.21-2-k7 #1 SMP Wed Jul 11 04:29:08 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: 80793600 vsize: 80793600 resident: 30625792 share: 15118336 rss: 30625792 rss_rlim: 4294967295
CPU usage: start_time: 1191031669 rtime: 222 utime: 205 stime: 17 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227008336 (LWP 26360)]
(no debugging symbols found)
0xb7f7e7f2 in ?? () from /lib/ld-linux.so.2

+ Trace 166310

Thread 1 (Thread -1227008336 (LWP 26360))

#0 ??
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /lib/ld-linux.so.2
#5 raise
from /lib/i686/cmov/libc.so.6
#6 abort
from /lib/i686/cmov/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_item_new_with_label
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_sequence_iter_is_begin
#12 g_sequence_iter_is_begin
#13 g_sequence_sort_changed_iter
#14 gtk_list_item_new_with_label
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_list_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_list_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#17 eel_mime_application_chooser_get_type
from /usr/lib/libeel-2-2.18.so
#18 eel_mime_application_chooser_new
from /usr/lib/libeel-2-2.18.so
#19 fm_properties_window_get_type
#20 nautilus_directory_schedule_dequeue_pending
#21 nautilus_directory_async_state_changed
#22 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 main
#0 ??
from /lib/ld-linux.so.2



----------- .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.0/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
--------------------------------------------------

Comment 1 André Klapper 2007-10-03 11:09:06 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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