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 518259 - crash in Open Folder: Waiting, nothing much
crash in Open Folder: Waiting, nothing much
Status: RESOLVED DUPLICATE of bug 420467
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-23 17:14 UTC by raddy2
Modified: 2008-02-24 10:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description raddy2 2008-02-23 17:14:29 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Waiting, nothing much


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

System: Linux 2.6.23-gentoo-r3 #11 SMP Thu Dec 27 10:20:03 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 108085248 vsize: 108085248 resident: 47656960 share: 21188608 rss: 47656960 rss_rlim: 4294967295
CPU usage: start_time: 1203780796 rtime: 997 utime: 939 stime: 58 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 0xb605a6e0 (LWP 8614)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 190198

Thread 1 (Thread 0xb605a6e0 (LWP 8614))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 gnome_vfs_uri_unref
    at gnome-vfs-uri.c line 1025
  • #10 _gnome_vfs_job_destroy_notify_result
    at gnome-vfs-job.c line 335
  • #11 dispatch_job_callback
    at gnome-vfs-job.c line 535
  • #12 g_idle_dispatch
    at gmain.c line 4132
  • #13 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #14 g_main_context_iterate
    at gmain.c line 2694
  • #15 IA__g_main_loop_run
    at gmain.c line 2898
  • #16 IA__gtk_main
    at gtkmain.c line 1163
  • #17 main
    at nautilus-main.c line 556
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #19 _start
  • #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
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-02-24 10:59:02 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 420467 ***