Ubuntu
gvfs package

gvfsd-smb crashed with SIGSEGV in smbc_free_context()

Bug #1132570 reported by Wayne Lloyd
90
This bug affects 18 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Sorry i have not been able to reproduce this error

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Sun Feb 24 22:29:02 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
InstallationDate: Installed on 2013-01-15 (40 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/13
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f0d61804e6c <smbc_free_context+60>: mov 0x430(%rax),%rbx
 PC (0x7f0d61804e6c) ok
 source "0x430(%rax)" (0x000005a0) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 smbc_free_context () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-smb crashed with SIGSEGV in smbc_free_context()
UpgradeStatus: Upgraded to raring on 2013-02-10 (13 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Wayne Lloyd (waynelloyd) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 smbc_free_context (context=0x7f0d50003200, shutdown_ctx=shutdown_ctx@entry=1) at libsmb/libsmb_context.c:249
 do_unmount (backend=0x1603000, job=0x1621e50, flags=<optimized out>, mount_source=<optimized out>) at gvfsbackendsmb.c:698
 run (job=<optimized out>) at gvfsjobunmount.c:172
 g_vfs_job_run (job=0x1621e50) at gvfsjob.c:197
 job_handler_callback (data=<optimized out>, user_data=<optimized out>) at gvfsdaemon.c:184

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Sebastien Bacher (seb128)
information type: Private → Public
Revision history for this message
Guntbert Reiter (guntbert) wrote :

Happened right now after trying to access a Windows share through a (functional) VPN. The first hint of something strange was nemo trying to open the remote directory via VLC...

Ubuntu 13.04, upgraded since "forever", Filemanager: nemo

Revision history for this message
EliCoten (launchpad-elicoten) wrote :

Happens if I try to access a Samba share over a VPN mounted through gvfs after an interruption in the VPN (e.g. if the computer has been put on standby and resumed, or if network access is interrupted for any other reason).

Revision history for this message
Donarsson (benjamin-schwarz) wrote :

Just had the same crash while accessing a Samba share on local network.

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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