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 484962 - crash in Open Folder: changing directory
crash in Open Folder: changing directory
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-09 08:11 UTC by aguru
Modified: 2007-10-13 00:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description aguru 2007-10-09 08:11:51 UTC 
Version: 2.18.3

What were you doing when the application crashed?
changing directory


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

System: Linux 2.6.22-gentoo-r5 #1 SMP PREEMPT Tue Aug 28 14:44:30 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gentoo

Memory status: size: 322789376 vsize: 322789376 resident: 36462592 share: 22888448 rss: 36462592 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191917090 rtime: 192 utime: 172 stime: 20 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/libthread_db.so.1".
(no debugging symbols found)
0x00002aef1d721c2f in waitpid () from /lib/libpthread.so.0

+ Trace 168951

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 funlockfile
    from /lib/libpthread.so.0
  • #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 nautilus_navigation_window_show_sidebar
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_override_class_closure
    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_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_override_class_closure
    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 nautilus_navigation_window_show_sidebar
  • #21 nautilus_directory_async_state_changed
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_check
    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 


----------- .xsession-errors ---------------------
** Message: drive = 6ad280
** Message: volume = 6ad020
** Message: drive = 6ad1a0
** Message: volume = 6ad4e0
** Message: drive = 6ad100
** Message: volume = 0
** Message: drive = 6ad060
** Message: volume = 6ad2c0
** Message: drive = 6a7780
** Message: volume = 6ad560
** Message: drive = 6a76e0
** Message: volume = 6ad000
** 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 Christian Kirbach 2007-10-13 00:17:17 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 ***