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 462184 - crash in Open Folder: trying to change to any ...
crash in Open Folder: trying to change to any ...
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-07-31 16:03 UTC by vadeemsu
Modified: 2007-07-31 21:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description vadeemsu 2007-07-31 16:03:23 UTC 
Version: 2.18.3

What were you doing when the application crashed?
trying to change to any directory by mouse click


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

System: Linux 2.6.22.1 #2 PREEMPT Wed Jul 18 14:19:55 IDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: AluminumAlloy-Volcanic
Icon Theme: Gion

Memory status: size: 348741632 vsize: 348741632 resident: 29962240 share: 16191488 rss: 29962240 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185895783 rtime: 208 utime: 185 stime: 23 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 47535579237152 (LWP 19934)]
0x00002b3bb6c6dc7f in waitpid () from /lib/libpthread.so.0

+ Trace 151851

Thread 1 (Thread 47535579237152 (LWP 19934))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #4 g_log
    from /usr/lib/libglib-2.0.so.0
  • #5 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #6 view_as_menu_switch_views_callback
    at nautilus-navigation-window.c line 834
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_combo_box_model_row_deleted
    at /build/buildd/gtk+2.0-2.11.6/gtk/gtkcombobox.c line 3084
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 IA__gtk_list_store_remove
    at /build/buildd/gtk+2.0-2.11.6/gtk/gtkliststore.c line 969
  • #17 IA__gtk_list_store_clear
    at /build/buildd/gtk+2.0-2.11.6/gtk/gtkliststore.c line 1167
  • #18 load_view_as_menu
    at nautilus-navigation-window.c line 884
  • #19 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1883
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 ??
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 IA__gtk_main
    at /build/buildd/gtk+2.0-2.11.6/gtk/gtkmain.c line 1144
  • #24 main
    at nautilus-main.c line 548
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
closing
closing
closing
** 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 Martin Wehner 2007-07-31 21:50:03 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 ***