VBoxHeadless crashed with SIGSEGV

Bug #1726987 reported by David H Sianturi
This bug report is a duplicate of:  Bug #1716870: VBoxHeadless crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Error when I Start Vagrant

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: virtualbox 5.1.30-dfsg-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 25 00:32:59 2017
ExecutablePath: /usr/lib/virtualbox/VBoxHeadless
InstallationDate: Installed on 2017-10-22 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/virtualbox/VBoxHeadless --comment homestead-7 --startvm 5befde7f-af64-4a3a-8fb8-b3e880700f20 --vrde config
SegvAnalysis:
 Segfault happened at: 0x7fa57c780f77: movzbl (%rcx,%rdx,1),%r15d
 PC (0x7fa57c780f77) ok
 source "(%rcx,%rdx,1)" (0x0001699a) not located in a known VMA region (needed readable region)!
 destination "%r15d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
 ?? () from /usr/lib/virtualbox/ExtensionPacks/VNC/linux.amd64/VBoxVNC.so
 ?? () from /usr/lib/virtualbox/components/VBoxC.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
Title: VBoxHeadless crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
David H Sianturi (davidhsianturi) 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 #1716870, 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.

Other bug subscribers

Remote bug watches

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