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 515199 - crash in Open Folder: same crash - looked at p...
crash in Open Folder: same crash - looked at p...
Status: RESOLVED DUPLICATE of bug 406462
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-08 13:22 UTC by mike
Modified: 2008-02-09 12:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description mike 2008-02-08 13:22:01 UTC 
Version: 2.20.0

What were you doing when the application crashed?
same crash - looked at properties of an NTFS drive


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

System: Linux 2.6.24-gentoo #1 SMP Fri Jan 25 17:01:56 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaSegPhault
Icon Theme: gnome

Memory status: size: 71000064 vsize: 71000064 resident: 31576064 share: 20008960 rss: 31576064 rss_rlim: 4294967295
CPU usage: start_time: 1202476898 rtime: 209 utime: 178 stime: 31 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 0xb6c5c8e0 (LWP 9537)]
0xb7fa6410 in __kernel_vsyscall ()

+ Trace 188535

Thread 1 (Thread 0xb6c5c8e0 (LWP 9537))

  • #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__gtk_widget_get_toplevel
    at gtkwidget.c line 7286
  • #10 gtk_widget_get_screen_unchecked
    at gtkwidget.c line 6584
  • #11 IA__gtk_widget_has_screen
    at gtkwidget.c line 6657
  • #12 recompute_idle_func
    at gtkentry.c line 3198
  • #13 gdk_threads_dispatch
    at gdk.c line 470
  • #14 g_idle_dispatch
    at gmain.c line 4142
  • #15 IA__g_main_context_dispatch
    at gmain.c line 2064
  • #16 g_main_context_iterate
    at gmain.c line 2697
  • #17 IA__g_main_loop_run
    at gmain.c line 2905
  • #18 IA__gtk_main
    at gtkmain.c line 1163
  • #19 main
    at nautilus-main.c line 556
  • #20 __libc_start_main
    at libc-start.c line 227
  • #21 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors (410920 sec old) ---------------------
** 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
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-02-09 12:25:08 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 406462 ***