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 496506 - crash in Open Folder: I just open a folder usi...
crash in Open Folder: I just open a folder usi...
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-11-13 17:41 UTC by aldogarcia
Modified: 2007-11-13 22:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description aldogarcia 2007-11-13 17:41:59 UTC 
Version: 2.18.1

What were you doing when the application crashed?
I just open a folder using "File Browser"


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

System: Linux 2.6.21-gentoo-r4 #11 Thu Aug 30 15:57:05 CDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Wasp

Memory status: size: 77668352 vsize: 77668352 resident: 26689536 share: 19034112 rss: 26689536 rss_rlim: 4294967295
CPU usage: start_time: 1194954011 rtime: 232 utime: 221 stime: 11 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 -1228183888 (LWP 6718)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 177476

Thread 1 (Thread -1228183888 (LWP 6718))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 *__GI_abort
    at abort.c line 88
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
  • #10 view_as_menu_switch_views_callback
    at nautilus-navigation-window.c line 834
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #12 IA__g_closure_invoke
    at gclosure.c line 490
  • #13 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #15 IA__g_signal_emit
    at gsignal.c line 2243
  • #16 gtk_combo_box_model_row_deleted
    at gtkcombobox.c line 3119
  • #17 IA__g_cclosure_marshal_VOID__BOXED
    at gmarshal.c line 566
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 IA__gtk_tree_model_row_deleted
    at gtktreemodel.c line 1537
  • #23 IA__gtk_list_store_remove
    at gtkliststore.c line 969
  • #24 IA__gtk_list_store_clear
    at gtkliststore.c line 1167
  • #25 load_view_as_menu
    at nautilus-navigation-window.c line 884
  • #26 ready_callback_call
    at nautilus-directory-async.c line 1265
  • #27 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1883
  • #28 g_idle_dispatch
    at gmain.c line 4132
  • #29 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #30 g_main_context_iterate
    at gmain.c line 2694
  • #31 IA__g_main_loop_run
    at gmain.c line 2898
  • #32 IA__gtk_main
    at gtkmain.c line 1146
  • #33 main
    at nautilus-main.c line 548
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
UPDATING SHAPE
CachingBackend: Saving <#Windowlist1> :) ...
OK
UPDATING SHAPE
UPDATING SHAPE
CachingBackend: Saving <#Windowlist1> :) ...
OK
UPDATING SHAPE
UPDATING SHAPE
CachingBackend: Saving <#Windowlist1> :) ...
OK
UPDATING SHAPE
UPDATING SHAPE
CachingBackend: Saving <#Windowlist1>Cannot access memory at address 0x1a3e
Cannot access memory at address 0x1a3e
--------------------------------------------------
Comment 1 André Klapper 2007-11-13 22:16:19 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 ***