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 494576 - crash in Computer: i right clicked on a fol...
crash in Computer: i right clicked on a fol...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-07 12:55 UTC by francre
Modified: 2007-11-07 20:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description francre 2007-11-07 12:55:18 UTC 
Version: 2.18.3

What were you doing when the application crashed?
i right clicked on a folder and chose properties


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

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Lush
Icon Theme: Lush

Memory status: size: 306253824 vsize: 306253824 resident: 34885632 share: 16293888 rss: 34885632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194440092 rtime: 140 utime: 128 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b314ea16bc0 (LWP 12274)]
0x00002b3147f9dc7f in waitpid () from /lib/libpthread.so.0

+ Trace 176030

Thread 1 (Thread 0x2b314ea16bc0 (LWP 12274))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 IA__g_logv
  • #6 IA__g_log
    at /build/buildd/glib2.0-2.14.1/glib/gmessages.c line 517
  • #7 IA__g_assert_warning
  • #8 gtk_list_store_compare_func
    at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1677
  • #9 node_find_closest
    at gsequence.c line 1136
  • #10 node_insert_sorted
    at gsequence.c line 1301
  • #11 g_sequence_sort_changed_iter
    at gsequence.c line 566
  • #12 gtk_list_store_sort_iter_changed
    at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1758
  • #13 IA__gtk_list_store_set_valist
    at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 901
  • #14 IA__gtk_list_store_set
    at /build/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 934
  • #15 ??
    from /usr/lib/libeel-2-2.18.so
  • #16 eel_mime_application_chooser_new
    from /usr/lib/libeel-2-2.18.so
  • #17 is_directory_ready_callback
    at fm-properties-window.c line 4436
  • #18 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1883
  • #19 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #20 g_main_context_iterate
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #21 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #22 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.1/gtk/gtkmain.c line 1146
  • #23 main
    at nautilus-main.c line 548
  • #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 André Klapper 2007-11-07 20:28:52 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 ***