gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

Bug #928492 reported by Blair Chasteen
76
This bug affects 16 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This happened after todays updates, I openeed nautilus and then this appeared.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.11.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic-pae 3.2.3
Uname: Linux 3.2.0-14-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Feb 7 15:24:08 2012
Disassembly: => 0xaaaaaaaa: Cannot access memory at address 0xaaaaaaaa
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.1 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xaaaaaaaa: Cannot access memory at address 0xaaaaaaaa
 PC (0xaaaaaaaa) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 g_vfs_job_run () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 g_thread_pool_thread_proxy (data=0x9005548) at /build/buildd/glib2.0-2.31.16/./glib/gthreadpool.c:317
 g_thread_proxy (data=0x9009030) at /build/buildd/glib2.0-2.31.16/./glib/gthread.c:801
Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
UpgradeStatus: Upgraded to precise on 2012-02-07 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare vboxusers

Revision history for this message
Blair Chasteen (darkstormyrain) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_vfs_job_run (job=0xb5918740) at gvfsjob.c:198
 job_handler_callback (data=0xb5918740, user_data=0x8ffbd18) at gvfsdaemon.c:144
 g_thread_pool_thread_proxy (data=0x9005548) at /build/buildd/glib2.0-2.31.16/./glib/gthreadpool.c:317
 g_thread_proxy (data=0x9009030) at /build/buildd/glib2.0-2.31.16/./glib/gthread.c:801

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-i386-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
Revision history for this message
Stefan Ivarsson (stefanivarsson) wrote :

Same on amd64. Happened when trying to import files from lacie NAS

Revision history for this message
brownknight (ramilclarin) wrote :

Got this error when I was trying to import files to Shotwell from a wireless network.

Revision history for this message
agoodm (alan-goodmanemail) wrote :

I believe I got this error while trying to import music files into banshe over wifi

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.