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 463367 - crash in File Browser: click for change folder
crash in File Browser: click for change folder
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-08-04 07:56 UTC by paal63
Modified: 2007-08-22 19:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description paal63 2007-08-04 07:56:20 UTC 
Version: 2.18.3

What were you doing when the application crashed?
click for change folder


Distribution: Ubuntu 5.10 (breezy)
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.17.4-vanilla #4 Tue Jul 18 13:12:24 CEST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Mist

Memory status: size: 79069184 vsize: 79069184 resident: 25968640 share: 13193216 rss: 25968640 rss_rlim: 4294967295
CPU usage: start_time: 1186214207 rtime: 555 utime: 523 stime: 32 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".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1227217232 (LWP 24621)]
0xb75f7bf1 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 152729

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #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_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_override_class_closure
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_combo_box_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-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_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 load_view_as_menu
    at nautilus-navigation-window.c line 884
  • #22 ready_callback_call
    at nautilus-directory-async.c line 1265
  • #23 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1883
  • #24 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 main
    at nautilus-main.c line 548 

Thread 1 (Thread -1227217232 (LWP 24621)):
#-1 0xb75f7bf1 in __waitpid_nocancel () from /lib/libpthread.so.0
No symbol table info available.
#-1 0xb75f7bf1 in __waitpid_nocancel () from /lib/libpthread.so.0
Comment 1 André Klapper 2007-08-22 19:22:46 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 ***