gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

Bug #1284591 reported by David Rosa
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

I had mapped a smb fileshare from a server, without disconnect the fileshare a connect to VPN, after disconnect VPN I try connect to fileshare and on this time crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gvfs-backends 1.19.5-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 25 12:11:39 2014
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
InstallationDate: Installed on 2014-02-20 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.3 /org/gtk/gvfs/exec_spaw/2
SegvAnalysis:
 Segfault happened at: 0x7f9639a806c5: cmpb $0x0,(%rax)
 PC (0x7f9639a806c5) ok
 source "$0x0" ok
 destination "(%rax)" (0x00000170) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
 ?? ()
 g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
David Rosa (davrosmen-7) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1160061, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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