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 491494 - crash in Open Folder: browsing the filesystem
crash in Open Folder: browsing the filesystem
Status: RESOLVED DUPLICATE of bug 459221
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-29 19:22 UTC by neosimago
Modified: 2007-10-30 00:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description neosimago 2007-10-29 19:22:32 UTC 
Version: 2.18.3

What were you doing when the application crashed?
browsing the filesystem


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-09-23 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r8-reiser4-nfs4-amd64 #3 SMP PREEMPT Tue Oct 2 02:02:43 PDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 437817344 vsize: 437817344 resident: 33615872 share: 20656128 rss: 33615872 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193685036 rtime: 788 utime: 599 stime: 189 cutime:68 cstime: 7 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 47396544328672 (LWP 13632)]
0x0000003521e0da1f in waitpid () from /lib/libpthread.so.0

+ Trace 173743

Thread 1 (Thread 47396544328672 (LWP 13632))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 view_as_menu_switch_views_callback
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_combo_box_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 load_view_as_menu
  • #21 call_ready_callbacks_at_idle
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (7 sec old) ---------------------
** 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
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-30 00:34:56 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 459221 ***