gvfsd-smb crashed with SIGSEGV in g_vfs_job_emit_finished()

Bug #921682 reported by Dario Panico
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

the crash happened while rhythmbox was scanning my music collection (which is stored on a gvfs drive) for the first time.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.10.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Jan 25 17:47:05 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120124)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/11
SegvAnalysis:
 Segfault happened at: 0x7ff43ae793c4 <g_vfs_job_emit_finished+4>: movzbl 0x28(%rdi),%eax
 PC (0x7ff43ae793c4) ok
 source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_vfs_job_emit_finished () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_emit_finished()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Dario Panico (dariopan) 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 #838464, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
Dario Panico (dariopan) wrote :

that bug doesn't exist!

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.