Bug 533641 – crash in Home Folder: Tentando entrar em um di...

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 533641 - crash in Home Folder: Tentando entrar em um di...


Summary:	crash in Home Folder: Tentando entrar em um di...


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-05-17 23:08 UTC by crysttian
Modified:	2008-05-18 07:05 UTC

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

Description crysttian 2008-05-17 23:08:32 UTC

What were you doing when the application crashed?
Tentando entrar em um diretorio da rede em um computador com windows xp.


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

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 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: 446287872 vsize: 446287872 resident: 34758656 share: 18432000 rss: 34758656 rss_rlim: 18446744073709551615
CPU usage: start_time: 1211065682 rtime: 346 utime: 327 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2aabfb78e400 (LWP 7287)]
[New Thread 0x40800950 (LWP 7317)]
(no debugging symbols found)
0x00002aabf4ca9edf in waitpid () from /lib/libpthread.so.0

+ Trace 197993

Thread 1 (Thread 0x2aabfb78e400 (LWP 7287))

#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 ??
#6 ??
from /usr/lib/libglib-2.0.so.0
#7 ??
#8 ??
#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 ??
#15 __libc_start_main
from /lib/libc.so.6
#16 ??
#17 ??
#18 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (57 sec old) ---------------------
Host: amule.sourceforge.net:80
URL: http://amule.sourceforge.net/lastversion
Response: 200 (Error: 0)
Download size: 6
HTTP download thread ended
Shutting down aMule...
aMule dialog destroyed
Now, exiting main app...
aMule OnExit: Terminating core.
Saving PartFile 1 of 4Saving PartFile 2 of 4Saving PartFile 3 of 4Saving PartFile 4 of 4
All PartFiles Saved.
aMule shutdown completed.
Could not start esd: Failed to execute child process "esd" (Arquivo ou diretório não encontrado)
seahorse nautilus module initialized
Initializing gnome-mount extension
--------------------------------------------------

Comment 1 A. Walton 2008-05-18 07:05:24 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 ***