nautilus crash when writing on smbfs

[Christoph Georgi]

Nautilus closes (crashes) whenever I copy a file to a mounted shared network
folder (WindowsXP) with read and write permissions. The folder is mounted in my
home directory, type smbfs, and options guest, fmask=0777, dmask=0777. Using the
terminal no errors occur when copying a file into that folder. The "report to
developers" window only opens unregularly after nautilus closed.

http://bugzilla.gnome.org/show_bug.cgi?id=158401: http://bugzilla.gnome.org/show_bug.cgi?id=158401

[Sebastien Bacher (seb128)]

could you provide a backtrace of the crash ?
(you can get it in the details of the bug-buddy dialog)

[Christoph Georgi (christoph-georgi)]

Sorry, I can't provide you with a backtrace as the report-the-bug windows
doesn't show up anymore. However, I found some more stuff that might help you:

Everytime when nautilus crashes the following error shows up in /var/log/messages:
> Nov 12 12:12:57 localhost kernel: smb_lookup: find //8030.2_info.doc failed,
error=-512
whereas 8030.2_info.doc is the file locally stored on /home/chg/desktop,
remotely on smb://workgroup/server/write_access

Nautilus does not crash when opening the remote folder via the smb://... path
and then copying files into the write_access folder.

Drag-and-Dropping the file into the mounted folder via the "tree" pane in
nautilus does not cause the browser to crash but makes the mounted folder
disappear. After reloading the folder containing the mounted folder, the
write_access folder can be seen and opened again.

I hope what I wrote is somehow understandable ;)

[Sebastien Bacher (seb128)]

are you using warty or hoary ? do you still get this crash ? getting a
backtrace would be nice, you can one in this way:
- ps ax | grep nautilus
- sudo gdb -p <pid> (where <pid> is the number return in the first column of
the first command)
(gdb) run
... get nautilus crashing
(gdb) thread apply all bt

[Christoph Georgi (christoph-georgi)]

I do get the bug still in warty. Here the backtrace (I hope I did it right) ;)

ps aux output:

chg 4917 1.4 6.1 31248 15680 ? Ss 11:03 0:01 nautilus
--sm-config-prefix /nautilus-SifXgE/ --sm-client-id
117f000001000110146534500000041300004 --screen 0

gdb:
Starting program: /usr/bin/nautilus
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...[Thread
debugging using libthread_db enabled]
[New Thread 1089450304 (LWP 5011)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...Detaching after fork from child process
5012.
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1099652016 (LWP 5018)]
Detaching after fork from child process 5019.
(no debugging symbols found)...(no debugging symbols found)...Detaching after
fork from child process 5028.
(no debugging symbols found)...(no debugging symbols found)...[New Thread
1100061616 (LWP 503...

[Sebastien Bacher (seb128)]

there is no crash according to the log. That seems to be this upstream bug:
http://bugzilla.gnome.org/show_bug.cgi?id=158401

Are you using warty or hoary ?

[Christoph Georgi (christoph-georgi)]

Jep, that seems to be the bug. I'm still using warty.

[Jason Toffaletti (jason)]

upstream bug marked as incomplete and closed. i'm closing this bug also, but
please reopen if you're still having this issue in breezy or dapper.