Bug 540970 – crash in Computer: Exploration d'un dossier...

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 540970 - crash in Computer: Exploration d'un dossier...


Summary:	crash in Computer: Exploration d'un dossier...


Status:	RESOLVED DUPLICATE of bug 522534

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-30 18:19 UTC by samy.mezani
Modified:	2008-06-30 20:40 UTC

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

Description samy.mezani 2008-06-30 18:19:30 UTC

Version: 2.20.0

What were you doing when the application crashed?
Exploration d'un dossier distant sur réseau Windows (Samba) dans Nautilus


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

System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Tangerine

Memory status: size: 73916416 vsize: 73916416 resident: 24182784 share: 15724544 rss: 24182784 rss_rlim: 4294967295
CPU usage: start_time: 1214849435 rtime: 659 utime: 314 stime: 345 cutime:0 cstime: 1 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bf8940 (LWP 3200)]
(no debugging symbols found)
0xffffe402 in __kernel_vsyscall ()

+ Trace 201781

Thread 1 (Thread 0xb6bf8940 (LWP 3200))

#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 ??
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 ??
#0 __kernel_vsyscall

Comment 1 A. Walton 2008-06-30 20:40:32 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 ***