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 546028 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-02 20:52 UTC by vadik56
Modified: 2008-08-04 15:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description vadik56 2008-08-02 20:52:23 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.20.3 2008-06-28 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-gentoo-r8 #2 SMP Mon Jun 23 23:34:50 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Noia

Memory status: size: 121286656 vsize: 121286656 resident: 56868864 share: 25497600 rss: 56868864 rss_rlim: 4294967295
CPU usage: start_time: 1217697856 rtime: 1682 utime: 1526 stime: 156 cutime:0 cstime: 4 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 0xb5ed5b10 (LWP 13368)]
0xb7f4f410 in __kernel_vsyscall ()

+ Trace 204443

Thread 1 (Thread 0xb5ed5b10 (LWP 13368))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 IA__g_str_hash
    at gstring.c line 95
  • #10 g_hash_table_remove_internal
    at ghash.c line 118
  • #11 remove_pending
    at fm-properties-window.c line 5063
  • #12 is_directory_ready_callback
    at fm-properties-window.c line 5085
  • #13 ready_callback_call
    at nautilus-directory-async.c line 1259
  • #14 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1877
  • #15 g_idle_dispatch
    at gmain.c line 4087
  • #16 IA__g_main_context_dispatch
    at gmain.c line 2009
  • #17 g_main_context_iterate
    at gmain.c line 2642
  • #18 IA__g_main_loop_run
    at gmain.c line 2850
  • #19 IA__gtk_main
    at gtkmain.c line 1163
  • #20 main
    at nautilus-main.c line 556
  • #21 __libc_start_main
    from /lib/libc.so.6
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(nautilus:13368): Eel-CRITICAL **: eel_timed_wait_stop: assertion `wait != NULL' failed
(nautilus:13368): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus:13368): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 A. Walton 2008-08-04 15:27:49 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 522534 ***