Virtualbox 2.1.0 on Hardy Heron. Vbox won't start. [Solved]

Discussions related to using VirtualBox on Linux hosts.
Post Reply
howls
Posts: 2
Joined: 19. Jan 2009, 10:46

Virtualbox 2.1.0 on Hardy Heron. Vbox won't start. [Solved]

Post by howls »

Greetings, I am getting an error when I try to start VirtualBox:

Code: Select all

VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: /usr/lib/libQtGui.so.4: undefined symbol: _ZN23QCoreApplicationPrivate19checkReceiverThreadEP7QObject
I have read the faq, it advised me to install a couple of font related packages, but these packages are already installed. I tried reinstalling libqt4-core, libqt4-gui, and virtualbox several times but this did not resolve the issue. I have also tried launching vbox as root and I still get this same message. Any help would be appreciated!
Last edited by howls on 21. Jan 2009, 06:59, edited 1 time in total.
Sasquatch
Volunteer
Posts: 17798
Joined: 17. Mar 2008, 13:41
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP, Windows 7, Linux
Location: /dev/random

Post by Sasquatch »

If you search the forum for this error, you will find other topics with different solutions. Those are not yet added to the FAQ.
See this google search for more info and help: http://www.google.com/search?q=supR3Har ... 1&filter=0
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
howls
Posts: 2
Joined: 19. Jan 2009, 10:46

Post by howls »

None of the other posts were of help to me.

It turns out I had some residual qt4 packages from a kde4 repository that was turned off in synaptic/apt. This lead to a mismatch between the libqt4-gui and libqt4-core (these came from the regular hardy repos) packages, and the rest of the qt4... files on my system (they came from a kde4 repo). I removed the qt4 packages (including residual configs) from the kde4 repo, then reinstalled the libqt4-gui and libqt4-core packages. This solved the problem.

Hope this helps someone else.
Post Reply