vbox install: Qt FATAL: cannot mix incompatible Qt libraries

English Applications
1

I had to to uninstall vbox to complete the latest core upgrade. I then installed vbox 5.1.8 from virtualbox.org. However I cannot install the ext-pack.

linux:/home/paco/Downloads # VirtualBox Oracle_VM_VirtualBox_Extension_Pack-5.1.8-111374.vbox-extpack      
Qt FATAL: Cannot mix incompatible Qt library (version 0x50402) with this library (version 0x50600)
Aborted

The extpack was downloaded from the vbox website at the same time as the 64-bit rpm.
I have Qt4 and Qt5 (need both) and they were installed using Yast.
I have updated all the Qt5 files using Yast but the error persists.

Machine details below:

2

Post:

zypper lr -d
3 
# | Alias               | Name                                           | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                | Service--+---------------------+------------------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------+--------
1 | 13.2                | vbox Oct 2016                                  | Yes     | ( p) Yes  | Yes     |   99     | rpm-md | http://download.virtualbox.org/virtualbox/rpm/opensuse/13.2        |        
2 | KDE_Qt5             | The Qt5 development repository (openSUSE_13.2) | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_13.2/  |        
3 | Packman_13.2        | Packman 13.2                                   | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_13.2/      |        
4 | google-chrome       | google-chrome                                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                |        
5 | qt5                 | qt5                                            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Qt55/openSUSE_13.2/ |        
6 | repo-non-oss        | openSUSE-13.2-Non-Oss                          | Yes     | ( p) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/non-oss/       |        
7 | repo-oss            | openSUSE-13.2-Oss                              | Yes     | ( p) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/oss/           |        
8 | repo-update         | openSUSE-13.2-Update                           | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.2/                          |        
9 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss                   | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.2-non-oss/
4

Well, that’s a good way to break your system:

Remove repo #5 and run “sudo zypper dup --from 2” to make sure all Qt packages have the same version.

Although I cannot guarantee you that VirtualBox will work then if using the one from Oracle, but it should.
At least openSUSE’s packages (both the standard one in 13.2 and the one from the Virtualization repo) work fine here with Qt 5.7.0 from KDE:Qt5.

PS: your actual problem is that you have some Qt 5.4 packages from the standard 13.2 update repo installed (mixed with the newer packages from the additional repos):

Qt FATAL: Cannot mix incompatible Qt library (version 0x50402) with this library (version 0x50600)

Though I have no idea where you have the Qt 5.6.0 package from at this point. You probably did not update in quite a while, or you installed packages from a third Qt repo that you removed meanwhile… :wink:

Anyway, the above “zypper dup” should fix that.

5

I followed the above and used Yast to check all the qt5 files are Qt 5.7.0. After that I installed vbox 5.1.8 and the corresponding extpack. The latter complained:

# VirtualBox Oracle_VM_VirtualBox_Extension_Pack-5.1.8-111374.vbox-extpack
Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile

but vbox manager appeared and I tried to add the existing guest (W10). That failed as follows:

# VirtualBox %UQt WARNING: libpng warning: iCCP: known incorrect sRGB profile
klauncher(12545) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
klauncher(12550) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
klauncher(12553) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(12517): couldn't create slave: "Cannot talk to klauncher: Not connected to D-Bus server" 
klauncher(12556) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
klauncher(12559) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(12517): couldn't create slave: "Cannot talk to klauncher: Not connected to D-Bus server" 
klauncher(12562) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
klauncher(12565) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(12517): couldn't create slave: "Cannot talk to klauncher: Not connected to D-Bus server" 
klauncher(12568) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(12517): Couldn't start knotify from knotify4.desktop:  "KLauncher could not be reached via D-Bus. Error when calling start_service_by_desktop_path:
Not connected to D-Bus server
" 


klauncher(12579) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
klauncher(12582) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(12517): couldn't create slave: "Cannot talk to klauncher: Not connected to D-Bus server" 
klauncher(12585) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
klauncher(12588) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(12517): couldn't create slave: "Cannot talk to klauncher: Not connected to D-Bus server" 
klauncher(12591) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
klauncher(12594) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
Qt CRITICAL: startkdeinitlock(12517): couldn't create slave: "Cannot talk to klauncher: Not connected to D-Bus server"
6

And what does this have to do with the problem discussed in this thread?
Have a look at the subject, the title is “vbox install: Qt FATAL: cannot mix incompatible Qt libraries”.

Your problem apparently is that you seemt to try running VirtualBox as root.
Don’t! Run it as user inside a graphical session. But you need to add your user to the “vboxusers” group first.

And why are you trying to run “VirtualBox Oracle_VM_VirtualBox_Extension_Pack-5.1.8-111374.vbox-extpack” or “VirtualBox %U”?
This won’t work either.
Just type in “VirtualBox”.

For further help, please open a new thread.
This one will be closed now.