Bug 538184 – crash in Home Folder:

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 538184 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 522534

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-13 18:44 UTC by alano.br
Modified:	2008-06-14 00:09 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description alano.br 2008-06-13 18:44:28 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 581873664 vsize: 581873664 resident: 54161408 share: 21889024 rss: 54161408 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213381405 rtime: 780 utime: 690 stime: 90 cutime:360 cstime: 63 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 0x2af310428240 (LWP 3682)]
0x00002af30991eedf in waitpid () from /lib/libpthread.so.0

+ Trace 200340

Thread 1 (Thread 0x2af310428240 (LWP 3682))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 istr_hash
at nautilus-directory-async.c line 170
#6 ??
from /usr/lib/libglib-2.0.so.0
#7 dequeue_pending_idle_callback
at nautilus-directory-async.c line 848
#8 directory_load_callback
at nautilus-directory-async.c line 1035
#9 ??
from /usr/lib/libgnomevfs-2.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 main
at nautilus-main.c line 556
#15 __libc_start_main
from /lib/libc.so.6
#16 _start
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (6 sec old) ---------------------
sh: dcop: command not found
sh: dcop: command not found
sh: dcop: command not found
sh: dcop: command not found
sh: dcop: command not found
sh: dcop: command not found
sh: dcop: command not found
sh: dcop: command not found
sh: dcop: command not found
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
sh: dcop: command not found
sh: dcop: command not found
--------------------------------------------------

Comment 1 Gianluca Borello 2008-06-14 00:09:12 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 522534 ***