[Pkg-virtualbox-devel] Bug#821157: virtualbox: Critical Error Failed to create the VirtualBoxClient COM object

Wed Apr 20 22:40:58 UTC 2016

Hi Gianfranco,

OK, I read the bug report at

    https://www.virtualbox.org/ticket/14296

Like mine, it mentions

    "Failed to create the VirtualBoxClient COM
    object"

Here's the big but.

BUT, UN-like my bug report, it

    1.) doesn't mention a corrupted
        .VirtualBox.xml file,

    2.) said VirtualBox complained with details of

            "REGDB_E_CLASSNOTREG (0x80040154)"

        in my case, VirtualBox complained with
        details of 

            "NS_ERROR_FAILURE (0x80004005)"

    3.) and assumes a Windows host.

        I found the bug after trying to run
        VirtualBox without its Linux kernel
        module.

I think it may be a different bug.

Does that make sense?

What do you think?

Thanks,
Kingsley

On 04/20/16 18:36, Gianfranco Costamagna wrote:
> control: tags -1 moreinfo
> 
> Hi, I would say you hit this bug
> https://www.virtualbox.org/ticket/14296can you please help upstream in fixing it if it is the case?
> 
> 
> (also trying upstream workaround fixes might help you and them)
> 
> thanks!
> Gianfranco
> 
> 
> 
> 
> Il Sabato 16 Aprile 2016 8:33, Kingsley G. Morse Jr. <kingsley at loaner.com> ha scritto:
> Package: virtualbox
> Version: 5.0.16-dfsg-2+b1
> Severity: normal
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
> 
>         # Qemu failed to install Windows 10 as a guest.
> 
>         # Some on-line reviewers wrote that VirtualBox
>         # is better.
> 
>         # I decided to try it.
> 
>         root:~ apt-get install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') virtualbox
> 
>         km:~ virtualbox
> 
>         # VirtualBox failed to run because it's kernel
>         # module was missing.
> 
>         root:~ apt-get install linux-headers-`uname -r`
>         root:~ aptitude install linux-source-4.4 apt-listchanges linux-image-686-pae
> 
>         # OK, now try running VirtualBox as a normal
>         # user
> 
>         km:~ virtualbox
> 
>         # VirtualBox openied a small window saying
> 
>             # VirtualBox - Critical Error
> 
>             # Failed to create the
>             # VirtualBoxClient COM object
> 
>             # The application will now terminate.
> 
>         # When I used the mouse's pointer to click on a
>         # small blue triangle in the small window, the
>         # following Details were revealed
> 
>             # Error in /home/kingsley/.VirtualBox/VirtualBox.xml (line 3) -- Cannot handle settings version '1.2-linux'.
>             # /build/virtualbox-f0lC84/virtualbox-5.0.16-dfsg/src/VBox/Main/src-server/VirtualBoxImpl.cpp[534] (nsresult VirtualBox::init()).
> 
>             # Result Code: NS_ERROR_FAILURE (0x80004005)
>             # Component:   VirtualBoxWrap
>             # Interface:   IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
> 
>         # See the attached screen shot.
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
>         # I'm not certain, but I wonder if trying
>         # to run VirtualBox without its kernel
>         # module corrupted ~/.VirtualBox
> 
>         # I seem to have fixed it by doing
> 
>         km:~ rm ~/.VirtualBox/*
>         km:~ rmdir ~/.VirtualBox
> 
>         km:~ virtualbox
> 
>         # See the attached screen shot.
> 
>    * What was the outcome of this action?
> 
>         # I danced back and forth from one foot to
>         # another, like a troll under a bridge.
> 
>    * What outcome did you expect instead?
> 
>         # Colorado's Republican Party to cancel
>         # voting.
> 
>         # Oops
> 
>         # Wait
> 
>         # They actually did that.
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages virtualbox depends on:
> ii  adduser                               3.113+nmu3
> ii  init-system-helpers                   1.24
> ii  libc6                                 2.22-6
> ii  libcurl3-gnutls                       7.47.0-1
> ii  libgcc1                               1:5.3.1-11
> ii  libgsoap8                             2.8.28-2
> ii  libpng16-16                           1.6.21-2
> ii  libpython2.7                          2.7.11-3
> ii  libsdl1.2debian                       1.2.15-12
> ii  libssl1.0.2                           1.0.2g-1
> ii  libstdc++6                            5.3.1-11
> ii  libvncserver1                         0.9.10+dfsg-3
> ii  libvpx3                               1.5.0-2
> ii  libx11-6                              2:1.6.3-1
> ii  libxcursor1                           1:1.1.14-1+b1
> ii  libxext6                              2:1.3.3-1
> ii  libxml2                               2.9.3+dfsg1-1
> ii  libxmu6                               2:1.1.2-1
> ii  libxt6                                1:1.1.5-1
> ii  procps                                2:3.3.10-4
> ii  python                                2.7.9-1
> ii  python2.7                             2.7.11-3
> pn  python:any                            <none>
> ii  virtualbox-dkms [virtualbox-modules]  5.0.16-dfsg-2
> ii  zlib1g                                1:1.2.8.dfsg-2+b1
> 
> Versions of packages virtualbox recommends:
> ii  libgl1-mesa-glx [libgl1]  11.1.2-1
> ii  libqt4-opengl             4:4.8.7+dfsg-3
> ii  libqtcore4                4:4.8.7+dfsg-3
> ii  libqtgui4                 4:4.8.7+dfsg-3
> ii  virtualbox-qt             5.0.16-dfsg-2+b1
> 
> Versions of packages virtualbox suggests:
> pn  vde2                            <none>
> pn  virtualbox-guest-additions-iso  <none>
> 
> -- no debconf information

-- 
Time is the fire in which we all burn.