gvfsd-afc crashed with SIGSEGV in g_vfs_job_try()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu precise (development branch)
Release: 12.04
gvfs:
Installed: 1.10.1-1ubuntu1
Candidate: 1.10.1-1ubuntu1
Version table:
*** 1.10.1-1ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.10.1-1ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-6-generic i686
NonfreeKernelMo
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Dec 30 01:07:48 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
DuplicateOf: https:/
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_US:en
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? ()
?? () from /usr/lib/
g_vfs_job_try () from /usr/lib/
g_vfs_
?? () from /usr/lib/
Title: gvfsd-afc crashed with SIGSEGV in g_vfs_job_try()
UpgradeStatus: Upgraded to precise on 2011-12-22 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #908350, 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.