Bug 534159 – crash in File Browser: opening a smb shared fol...

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 534159 - crash in File Browser: opening a smb shared fol...


Summary:	crash in File Browser: opening a smb shared fol...


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-21 08:01 UTC by cionfolinet
Modified:	2008-05-21 09:25 UTC

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

Description cionfolinet 2008-05-21 08:01:45 UTC

Version: 2.20.0

What were you doing when the application crashed?
opening a smb shared folder


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

System: Linux 2.6.22-20071024 #1 SMP Wed Oct 24 15:31:30 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: Lush

Memory status: size: 84795392 vsize: 84795392 resident: 31080448 share: 18497536 rss: 31080448 rss_rlim: 4294967295
CPU usage: start_time: 1211355103 rtime: 577 utime: 543 stime: 34 cutime:4 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 0xb6a80720 (LWP 4394)]
[New Thread 0xb36b2b90 (LWP 4826)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198285

Thread 1 (Thread 0xb6a80720 (LWP 4394))

#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 Cosimo Cecchi 2008-05-21 09:25:37 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 522534 ***