Bug 531934 – crash in Open Folder: browsing samba folder

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 531934 - crash in Open Folder: browsing samba folder


Summary:	crash in Open Folder: browsing samba folder


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 12:17 UTC by vesavan
Modified:	2008-05-07 12:19 UTC

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

Description vesavan 2008-05-07 12:17:41 UTC

Version: 2.20.0

What were you doing when the application crashed?
browsing samba folder


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: Clearlooks
Icon Theme: gnome

Memory status: size: 463335424 vsize: 463335424 resident: 49557504 share: 18853888 rss: 49557504 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210162196 rtime: 847 utime: 797 stime: 50 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 0x2b7cad36ab80 (LWP 22098)]
[New Thread 0x41001950 (LWP 22363)]
(no debugging symbols found)
0x00002b7ca6e8fedf in waitpid () from /lib/libpthread.so.0

+ Trace 197121

Thread 1 (Thread 0x2b7cad36ab80 (LWP 22098))

#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 (428 sec old) ---------------------
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0xe03ff5 (DataCard o); these messages lack timestamps and therefore suck.
** (nautilus:4064): WARNING **: No description found for mime type "x-directory/smb-share" (file is "proj"), please tell the gnome-vfs mailing list.
(gnome-appearance-properties:21951): appearance-properties-WARNING **: Unknown Tag: comment
(gnome-appearance-properties:21951): appearance-properties-WARNING **: Unknown Tag: comment
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0xe0c538 (in0718 on ); these messages lack timestamps and therefore suck.
Initializing gnome-mount extension
seahorse nautilus module initialized
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0xe0014f (vesa); these messages lack timestamps and therefore suck.
Initializing gnome-mount extension
seahorse nautilus module initialized
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-07 12:19:55 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 ***