2.2.0 SVN 4/7/09 - build ok and runtime fatal error

Postings relating to old VirtualBox pre-releases
Post Reply
es1
Posts: 38
Joined: 25. Mar 2009, 02:12
Primary OS: Fedora 10
VBox Version: OSE self-compiled
Guest OSses: XP,Vista,Linux,win7,32b,64b

2.2.0 SVN 4/7/09 - build ok and runtime fatal error

Post by es1 »

I checked out the sources from the svn repositoy and build them successfully on Fedora 10 with latest updates.
When I try to Edit the properties of a virtual machine, without trying to run it, I get error message box:

Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)

It is the same issue as http://forums.virtualbox.org/viewtopic.php?f=15&t=16048
The about box shows: VirtualBox 2.2.1_OSE r18840 8)
frank
Oracle Corporation
Posts: 3362
Joined: 7. Jun 2007, 09:11
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows
Location: Dresden, Germany
Contact:

Re: 2.2.0 SVN 4/7/09 - build ok and runtime fatal error

Post by frank »

Unfortunately I was still not able to reproduce the problem. Didn't have time to install Fedora 10 though ...
frank
Oracle Corporation
Posts: 3362
Joined: 7. Jun 2007, 09:11
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows
Location: Dresden, Germany
Contact:

Re: 2.2.0 SVN 4/7/09 - build ok and runtime fatal error

Post by frank »

Please could you check our F9/F10 package for 2.2.0 as well when it is uploaded (should be done in a few hours)?
es1
Posts: 38
Joined: 25. Mar 2009, 02:12
Primary OS: Fedora 10
VBox Version: OSE self-compiled
Guest OSses: XP,Vista,Linux,win7,32b,64b

Re: 2.2.0 SVN 4/7/09 - build ok and runtime fatal error

Post by es1 »

Hi Frank,
Thank you for your reply, it works with the your binaries of the beta, but not with the self compiled.
I'll check as soon as I can download the new sources.
Thanks 8)
frank
Oracle Corporation
Posts: 3362
Joined: 7. Jun 2007, 09:11
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows
Location: Dresden, Germany
Contact:

Re: 2.2.0 SVN 4/7/09 - build ok and runtime fatal error

Post by frank »

Please could you try if this is fixed with the OSE code of 2.2.2?
Post Reply