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 520951 - [browser mode] click "Empty Trash" button in trash folder, nautilus crashes
[browser mode] click "Empty Trash" button in trash folder, nautilus crashes
Status: RESOLVED DUPLICATE of bug 519050
Product: nautilus
Classification: Core
Component: [obsolete] GIO
2.21.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-07 11:00 UTC by sangu
Modified: 2008-03-07 11:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description sangu 2008-03-07 11:00:16 UTC 
Steps to reproduce:
1. Launch nautilus browser mode.
2. Click trash folder
3.  Click "Empty Trash" button


Stack trace:
Distribution: Fedora release 8.90 (Rawhide)
Gnome Release: 2.21.92 2008-03-02 (Red Hat, Inc)
BugBuddy Version: 2.21.90

System: Linux 2.6.24.1-28.fc9 #1 SMP Sun Feb 10 17:27:37 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 135815168 vsize: 135815168 resident: 47939584 share: 24350720 rss: 47939584 rss_rlim: 4294967295
CPU usage: start_time: 1204885893 rtime: 831 utime: 719 stime: 112 cutime:2 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Getting all the debuginfos: debuginfo-install nautilus
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fb8730 (LWP 20409)]
[New Thread 0xb7af3b90 (LWP 20712)]
[New Thread 0xb70ebb90 (LWP 20414)]
0x00131402 in __kernel_vsyscall ()

+ Trace 191615

Thread 1 (Thread 0xb7fb8730 (LWP 20409))

  • #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 226
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
  • #8 <signal handler called>
  • #9 trash_state_changed_cb
    at nautilus-pathbar.c line 211
  • #10 IA__g_cclosure_marshal_VOID__BOOLEAN
    at gmarshal.c line 111
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 update_info_cb
    at nautilus-trash-monitor.c line 128
  • #16 IA__g_simple_async_result_complete
    at gsimpleasyncresult.c line 553
  • #17 query_info_async_cb
    at gdaemonfile.c line 803
  • #18 async_path_call_done
    at gdaemonfile.c line 563
  • #19 async_call_finish
    at gvfsdaemondbus.c line 428
  • #20 handle_async_reply
    at gdbusutils.c line 1283
  • #21 _dbus_pending_call_complete
    at dbus-pending-call.c line 198
  • #22 complete_pending_call_and_unlock
    at dbus-connection.c line 2200
  • #23 dbus_connection_dispatch
    at dbus-connection.c line 4325
  • #24 dbus_source_dispatch
    at gdbusutils.c line 868
  • #25 IA__g_main_context_dispatch
    at gmain.c line 2065
  • #26 g_main_context_iterate
    at gmain.c line 2698
  • #27 IA__g_main_loop_run
    at gmain.c line 2906
  • #28 IA__gtk_main
    at gtkmain.c line 1163
  • #29 main
    at nautilus-main.c line 569
  • #0 __kernel_vsyscall 


Other information:
OS Fedora development (rawhide 20080307)
nautilus-2.21.92-2.fc9.i386
gvfs-0.1.11-2.fc9.i386
glib2-2.15.6-2.fc9.i386
Comment 1 Cosimo Cecchi 2008-03-07 11:08:10 UTC 
This is fixed in SVN now.

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 519050 ***