gvfsd-smb crashed with SIGSEGV in g_simple_async_result_complete()

Bug #451841 reported by Nicolay Doytchev
86
This bug affects 16 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

This bug exists in Jaunty and the steps to reproduce are the same as for Karmic. Fortunately it is a tad more stable in Karmic but it gvfs-smb crashed eventually today. Reproduce as follows:

0. Mount a remote smb share via Nautilus.
1. Open Rhythmbox / Exaile / (maybe other software that can generate a lot of traffic over smb).
2. Import a folder from the smb share into Rhythmbox / Exaile which contains a lot of music (the one tested here is over 200GB)
3. Wait.
4. Somewhere along the way the smb share will silently unmount and the import process will stop. The only trace of what happened will be visible via dmesg "gvfsd-smb[1873]: segfault at 14 ip 080583f5 sp bfbe2460 error 4 in gvfsd-smb[8048000+20000]" or Apport.

This crash occurs on my setup somewhere between 3GB and 20GB music imported.

I am sure that this bug is not specifically related with music files and importing in players but it is a generic bug in gvfs-smb which is triggered after some amount of data is transferred by it.

ProblemType: Crash
Architecture: i386
Date: Wed Oct 14 19:58:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
Package: gvfs-backends 1.4.0-0ubuntu4
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
SegvAnalysis:
 Segfault happened at: 0x80583f5: movzbl 0x14(%eax),%edx
 PC (0x080583f5) ok
 source "0x14(%eax)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
Title: gvfsd-smb crashed with SIGSEGV in g_simple_async_result_complete()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Nicolay Doytchev (lightrush) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:g_vfs_job_emit_finished (job=0x0) at gvfsjob.c:323
send_reply_cb (source_object=0x8edccc8, res=0x8edc4e0,
?? () from /usr/lib/libgio-2.0.so.0
g_simple_async_result_complete ()
?? () from /usr/lib/libgio-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Nicolay Doytchev (lightrush) wrote :

I have successfully reproduced it again.

I have installed Valgrind and the debug debs for gvfs and gvfs-backends. I have read how to run Valgrind but gvfs is started in a more complicated way than regular program. If you give specific instructions about doing something that will give more light on this bug I would gladly follow them.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in gvfs (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Revision history for this message
Sebastien Bacher (seb128) wrote :

you can find details on valgrind use there, https://wiki.ubuntu.com/Valgrind
the way to valgrind those usually is to rename the binary and set a wrapper calling valgrind on the real binary instead

Revision history for this message
Nicolay Doytchev (lightrush) wrote :

Elegant... Will try it and post the log. I do not program C yet so I have no clue how and if this will be helpful but according to https://wiki.ubuntu.com/Valgrind , this is what I have to do next if I see a segfault. I hope it helps. I could also submit a bugreport upstream. Is it possible to patch this before release if there is enough useful information?

Revision history for this message
Nicolay Doytchev (lightrush) wrote :

Creating a wrapper starts the daemon but then the daemon begins to spit DBUS errors and does not function properly. Help?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you give details on the error?

Revision history for this message
Nicolay Doytchev (lightrush) wrote :

Could not open location 'smb://lr-gassus/usb/'

DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

The message appears in a dialog box with a Close button.

Revision history for this message
Nicolay Doytchev (lightrush) wrote :

I think this error appears since gvfsd tries to communicate to gvfsd-smb via DBus but since this is no longer the executable of the program the connection cannot be established. If my understanding is right... I am not familiar with the DBus and GTK APIs. Still grinding Java here... C is coming next semester.

Revision history for this message
Nicolay Doytchev (lightrush) wrote :

Still here in 1.4.1

Revision history for this message
yannack (yannack) wrote :

I experience the same problem (I think). I try copying files from a nautilus SMB share to a nautilus FTP share, and I usually cannot go further than about 500MB (because the SMB share fails, not the FTP)
I try reading musing from the SMB share, sometimes it will stop playing within a few minutes, sometimes longer.
I also believe that suspending the computer will also create the same problem.

Sometimes I am lucky and Nautilus lets me unmount the SMB share and remount it, but most of the time, I have to kill nautilus, because I get the same error message.

Here is what I get through the command line.
gvfs-mount -u smb://admin@192.168.0.125/video/
Error unmounting mount: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this reproducible with Lucid? Please test and provide us of feedback about it, Thanks in advance..

Changed in gvfs (Ubuntu):
status: New → Incomplete
importance: Medium → Low
Revision history for this message
Nicolay Doytchev (lightrush) wrote :

I will test it out today and report back.

Revision history for this message
Nicolay Doytchev (lightrush) wrote :

The bug does not exist/affect me any more. A full 250GB collection can be imported in Exaile over SMB share without crashing gvfs-smb.

Revision history for this message
Nicolay Doytchev (lightrush) wrote :

*Tested on Lucid Beta1 + latest updates.

No EDIT button == double post :|

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for the update, closing the bug since that works now

Changed in gvfs (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
JM (jsmrkhm) wrote :

Apologies if I've submitted this to the wrong place, but I appear to be getting exactly the same error in Maverick Meerkat:

uname -a
Linux -------pc 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linux

dmesg|grep error
gvfsd-smb[4331]: segfault at 18 ip 0000000000410304 sp 00007fff8b10d960 error 4 in gvfsd-smb[400000+25000]
gvfsd-smb[4421]: segfault at 18 ip 0000000000410304 sp 00007fff653f8860 error 4 in gvfsd-smb[400000+25000]
gvfsd-smb[4504]: segfault at 18 ip 0000000000410304 sp 00007ffff8b8fe20 error 4 in gvfsd-smb[400000+25000]
...and so on...

(However, this OS is Linux Mint 10, does that mean all responsibility on this site is denied? ;-)

Revision history for this message
Taras Perebeynosov (taras-perebeynosov) wrote :

Error reproduced in 12.04

Revision history for this message
Lupius (lupius) wrote :

Same bug occured in 12.04 LTS beta fully updated up to 08.04 while trying to play an mp3 located on windows network share via rhytmbox.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.