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 508182 - crash in Computer: Nautilus was opened, I s...
crash in Computer: Nautilus was opened, I s...
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: 2008-01-08 23:21 UTC by la.poubelle.a.jean
Modified: 2008-01-09 08:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description la.poubelle.a.jean 2008-01-08 23:21:03 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Nautilus was opened, I started a search request using nautilus search tool and it told me it couldn't display the directory, then I clicked on the "+" symbol on the right of the search toolbar, selected "File type" instead of location and when I selected "Any file type" nautilus crashed


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

System: Linux 2.6.21.070829 #1 SMP PREEMPT Wed Aug 29 22:46:20 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Buuf-Deuce

Memory status: size: 98119680 vsize: 98119680 resident: 30715904 share: 16883712 rss: 30715904 rss_rlim: 4294967295
CPU usage: start_time: 1199775406 rtime: 3172 utime: 2947 stime: 225 cutime:3 cstime: 5 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 0xb6df26b0 (LWP 3673)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 184602

Thread 1 (Thread 0xb6df26b0 (LWP 3673))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** (nautilus:3673): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed
** (nautilus:3673): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed
** (nautilus:3673): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed
** (nautilus:3673): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed
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 Cosimo Cecchi 2008-01-09 08:39:07 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 ***