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 519779 - crash in Open Folder: trying to empty trash
crash in Open Folder: trying to empty trash
Status: RESOLVED DUPLICATE of bug 519050
Product: nautilus
Classification: Core
Component: general
2.21.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-01 18:32 UTC by thanate
Modified: 2008-03-02 12:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description thanate 2008-03-01 18:32:21 UTC 
Version: 2.21.92

What were you doing when the application crashed?
trying to empty trash


Distribution: Debian lenny/sid
Gnome Release: 2.21.92 2008-02-29 (GARNOME)
BugBuddy Version: 2.21.90

System: Linux 2.6.23.14 #1 SMP PREEMPT Wed Jan 23 15:46:50 MST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 544079872 vsize: 544079872 resident: 55021568 share: 19693568 rss: 55021568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1204396304 rtime: 221 utime: 201 stime: 20 cutime:8 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/home/boat/garnome/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b528c3b15e0 (LWP 2569)]
[New Thread 0x42003950 (LWP 2579)]
[New Thread 0x40800950 (LWP 2575)]
0x00002b5289fad5ef in waitpid () from /lib/libpthread.so.0

+ Trace 190977

Thread 1 (Thread 0x2b528c3b15e0 (LWP 2569))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #3 bugbuddy_segv_handle
    at gnome-breakpad.cc line 213
  • #4 <signal handler called>
  • #5 trash_state_changed_cb
    at nautilus-pathbar.c line 211
  • #6 IA__g_closure_invoke
    at gclosure.c line 490
  • #7 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #8 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #9 IA__g_signal_emit
    at gsignal.c line 2243
  • #10 update_info_cb
    at nautilus-trash-monitor.c line 128
  • #11 query_info_async_cb
    at gdaemonfile.c line 803
  • #12 async_path_call_done
    at gdaemonfile.c line 563
  • #13 async_call_finish
    at gvfsdaemondbus.c line 428
  • #14 handle_async_reply
    at gdbusutils.c line 1245
  • #15 complete_pending_call_and_unlock
    at dbus-connection.c line 2170
  • #16 dbus_connection_dispatch
    at dbus-connection.c line 4296
  • #17 dbus_source_dispatch
    at gdbusutils.c line 836
  • #18 IA__g_main_context_dispatch
    at gmain.c line 2065
  • #19 g_main_context_iterate
    at gmain.c line 2698
  • #20 IA__g_main_loop_run
    at gmain.c line 2906
  • #21 IA__gtk_main
    at gtkmain.c line 1163
  • #22 main
    at nautilus-main.c line 569
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
** (gnome-mount:2574): WARNING **: Mount failed for /org/freedesktop/Hal/devices/volume_part1_size_6284081664
org.freedesktop.DBus.Error.AccessDenied : A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interfac
** (gnome-mount:2574): WARNING **: FIXME: Need to shutdown linc connections ...
** (gnome-mount:2576): WARNING **: FIXME: Need to shutdown linc connections ...
** (nautilus:2569): WARNING **: Unable to add monitor: Not supported
** (gecko:1928): WARNING **: FIXME: Need to shutdown linc connections ...
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff293fe000
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-02 12:15:42 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 519050 ***