Ubuntu
virtualbox package

resume fails with Failed to open a session for the virtual machine Win7. No error info. Result Code: NS_ERROR_CALL_FAILED (0x800706BE) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

Bug #1198664 reported by ts on 2013-07-07

This bug report is a duplicate of: Bug #1307093: VirtualBox saved VM resume causes SEGFAULT in i965_dri.so. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Virtualbox	Unknown	Unknown	virtualbox-trac #11938
	virtualbox (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

It's been a while that VirtualBox does not resume any VMs anymore.
Tried the "USB-Filter" solution, the 2D- and 3D- acceleration solution, added the user to the vboxusers group, but all to no avail.
Tried apt-get remove --purge virtualbox* and reinstalled. Same behavior. I have no fglrx driver (but intel).
The machine crashes upon resume, always with the same error

Failed to open a session for the virtual machine Win7.

No error info.

Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04

apt-cache policy virtualbox
virtualbox:
  Installed: 4.2.10-dfsg-0ubuntu2
  Candidate: 4.2.10-dfsg-0ubuntu2
  Version table:
*** 4.2.10-dfsg-0ubuntu2 0
        990 http://de.archive.ubuntu.com/ubuntu/ raring/multiverse amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: virtualbox 4.2.10-dfsg-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sun Jul 7 15:39:23 2013
InstallationDate: Installed on 2012-12-17 (201 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
SourcePackage: virtualbox
UpgradeStatus: Upgraded to raring on 2013-05-07 (61 days ago)

Tags:

Revision history for this message

ts (toto-23) wrote on 2013-07-07:

Dependencies.txt Edit (6.6 KiB, text/plain; charset="utf-8")
LsMod.txt Edit (4.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (106 bytes, text/plain; charset="utf-8")
VirtualBox.DpkgList.txt Edit (1.6 KiB, text/plain; charset="utf-8")
VirtualBox.ModInfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Carsten Oberscheid (carsten-c) wrote on 2013-11-14:

I have this problem on my new Ubuntu 13.10 install. No problems before on 12.04. Both with Unity.

A few days ago I found in a thread somewhere else (VirtualBox forums? Forgot to bookmark and can't find it now ...) that this only happens when the VM is stopped by closing the VM window by keyboard shortcut (Alt-F4 or Ctrl-Q). Close the window by clicking the (x) or using the window menu, and the VM will resume successfully.

Still annoying as heck, because I /always/ close Windows with ctrl-q and can't get used to do it the other way. Whether this is a VirtualBox bug or an Ubuntu/Unity bug, I don't know.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-11-08:

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