Bug 634976 – Crash on closing trash

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 634976 - Crash on closing trash


Summary:	Crash on closing trash


Status:	RESOLVED DUPLICATE of bug 620866

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.32.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-11-16 11:19 UTC by Maciej (Matthew) Piechotka
Modified:	2010-11-16 14:25 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Maciej (Matthew) Piechotka 2010-11-16 11:19:16 UTC

Distribution: Gentoo Base System release 2.0.1-r1
Gnome Release: 2.32.0 2010-11-04 (Gentoo)
BugBuddy Version: 2.32.0

System: Linux 2.6.36-zen1+ #8 ZEN SMP PREEMPT Sun Nov 14 02:05:51 GMT 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10902000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango
GTK+ Modules: canberra-gtk-module, gnomesegvhandler, gnomebreakpad

Memory status: size: 543801344 vsize: 543801344 resident: 33001472 share: 23912448 rss: 33001472 rss_rlim: 18446744073709551615
CPU usage: start_time: 1289850963 rtime: 351 utime: 339 stime: 12 cutime:13 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fca68fdc710 (LWP 3260)]
0x00007fca721c502d in waitpid () from /lib/libpthread.so.0

+ Trace 224700

Thread 1 (Thread 0x7fca752a7780 (LWP 3223))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
at gspawn.c line 392
#2 g_spawn_command_line_sync
at gspawn.c line 706
#3 run_bug_buddy
at gnome-segvhanlder.c line 240
#4 bugbuddy_segv_handle
at gnome-segvhanlder.c line 191
#5 <signal handler called>
#6 tags_view_query_files_for_tag_id_cb
at tracker-tags-view.c line 304
#7 callback_with_gptrarray
at tracker.c line 579
#8 org_freedesktop_Tracker1_Resources_sparql_query_async_callback
at tracker-resources-glue.h line 81
#9 complete_pending_call_and_unlock
at /var/tmp/paludis/sys-apps-dbus-1.4.0/work/dbus-1.4.0/dbus/dbus-connection.c line 2311
#10 dbus_connection_dispatch
at /var/tmp/paludis/sys-apps-dbus-1.4.0/work/dbus-1.4.0/dbus/dbus-connection.c line 4596
#11 message_queue_dispatch
at /var/tmp/paludis/dev-libs-dbus-glib-0.88/work/dbus-glib-0.88/dbus/dbus-gmain.c line 101
#12 g_main_dispatch
at gmain.c line 2149
#13 g_main_context_dispatch
at gmain.c line 2702
#14 g_main_context_iterate
at gmain.c line 2780
#15 g_main_loop_run
at gmain.c line 2988
#16 IA__gtk_main
at gtkmain.c line 1237
#17 main
at nautilus-main.c line 544


	Inferior 1 [process 3223] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (52005 sec old) ---------------------
(evolution:3245): camel-WARNING **: Error message was: Connection reset by peer
(evolution:3245): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Connection reset by peer
(evolution:3245): evolution-mail-WARNING **: Failed to refresh folders: NNTP Command failed: Connection reset by peer
(evolution:3245): camel-WARNING **: CamelTcpStreamSSL::write() set its GError but then reported success
(evolution:3245): camel-WARNING **: Error message was: Connection reset by peer
(evolution:3245): camel-WARNING **: CamelNNTPStream::write() set its GError b
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2010-11-16 14:25:07 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 bug 620866 ***