Bug 536064 – crash in Computer:

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 536064 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 480179

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-01 14:32 UTC by damien.courousse
Modified:	2008-06-02 09:06 UTC

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

Description damien.courousse 2008-06-01 14:32:24 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Vista-Gray
Icon Theme: Vista

Memory status: size: 73744384 vsize: 73744384 resident: 17723392 share: 13275136 rss: 17723392 rss_rlim: 4294967295
CPU usage: start_time: 1212330786 rtime: 43 utime: 33 stime: 10 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/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b45720 (LWP 15214)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 199329

Thread 1 (Thread 0xb6b45720 (LWP 15214))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 gconf_client_remove_dir
from /usr/lib/libgconf-2.so.4
#7 ??
from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
#8 ??
#9 ??
from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
#10 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
/bin/sh: /usr/bin/esd: Aucun fichier ou répertoire de ce type
--------------------------------------------------

Comment 1 A. Walton 2008-06-02 09:06:39 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 480179 ***