Bug 532000 – crash in Computer: accéder a un répertoire ...

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 532000 - crash in Computer: accéder a un répertoire ...


Summary:	crash in Computer: accéder a un répertoire ...


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-05-07 17:25 UTC by adoubeur
Modified:	2008-05-07 17:30 UTC

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

Description adoubeur 2008-05-07 17:25:06 UTC

Version: 2.20.0

What were you doing when the application crashed?
accéder a un répertoire partagé sur un PC (Windows XP) via Nautilus


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 Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 84090880 vsize: 84090880 resident: 29249536 share: 16822272 rss: 29249536 rss_rlim: 4294967295
CPU usage: start_time: 1210181013 rtime: 379 utime: 348 stime: 31 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c0c720 (LWP 3620)]
[New Thread 0xb4affb90 (LWP 3704)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197147

Thread 1 (Thread 0xb6c0c720 (LWP 3620))

#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



----------- .xsession-errors ---------------------
m| 10000
not rec
:images/both-good-signal-lock.png
|idle-good-signal-lock.png
 wlan0:   36917     180    0    0    0     0          0         0    47885     320    0    0    0     0       0          0
not trans
0
m| 10000
not rec
:images/idle-good-signal-lock.png
|idle-good-signal-lock.png
 wlan0:   38113     188    0    0    0     0          0         0    49542     331    0    0    0     0       0          0
not rec
:images/idle-good-signal-lock.png
|transmitting-good-signal-lock.png
 wlan0:   39359     192    0    0    0     0          0         0    5
--------------------------------------------------

Comment 1 Paweł Paprota 2008-05-07 17:30:06 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 ***