-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mixing incompatible Qt library (version 0x50902) with this library (version 0x50901) #30551
Comments
As I said in #30255, I experience the same problem with qutebrowser. But, if I install the exact same qutebrowser package in my user environment instead of the global one, it works:
Regarding @ttuegel's remark about the user environment: I don't have anything installed in my user environment (and why could that even be the problem? Shouldn't the dependencies be independent of the environment?). |
FYI there is a thread on Archlinux forum on this issue: It seems that @yrashk is right about the root cause of the problem: the mix of two Qt version. |
Yes, you cannot have anything installed with Qt 5.9.1 and Qt 5.9.2 at the same time. This is mainly a NixOS problem, which I will explain in a moment. However: QtWebkit is not part of Qt anymore, so the QtWebkit version has nothing whatsoever to do with the Qt version. Our QtWebkit 5.9.1 is built with Qt 5.9.2. As @Eisfreak7 found by installing qutebrowser into a user profile, the problem is not QtWebkit 5.9.1, but something else in your system is pulling in Qt 5.9.1.
No, not for Qt programs. Qt loads plugins at runtime for most features. We let it search your environment for plugins so that you can do things like use themes and run Qt applications outside KDE. Unfortunately, Qt freaks out if it even sees an old plugin, so if you have anything old hanging around it will cause problems. This problem can be circumvented by installing something in the user profile because that profile will be searched first (so if Qt finds the plugin it needs in the user environment, it never runs into the bad plugin in the global environment).
@Eisfreak7 |
I tried to First I ran
So it looks like my current profile links to the old Qt plugins as expected.
And I found out that the PyQt library, that is installed in my python environment, is linked to the old Qt library. Still there is a problem here: python installed environment contains libraries that are not updated by To be clear I installed the environment using
After remove, when I re-install the environment It gets updated correctly. |
I have this with VirtualBox, too. :-( I can’t find what is causing it. |
Same problem here. |
If I have
I get https://gist.github.com/ebzzry/3dba05831d2652b37e6065d6899cd232. When I install VirtualBox via nix-env, then run it:
I get and |
Your VirtualBox is loading outdated plugins from your system environment: https://gist.github.com/ebzzry/3dba05831d2652b37e6065d6899cd232#file-virtualbox-strace-txt-L1514 and so on... It works if installed in the user profile because the plugins from the user profile supersede those in the system profile. Something installed in the system profile is pulling in outdated plugins, though I cannot tell what is. |
Oh. Is that so. I wonder what it is. :-( |
I found that if I have an environment based on a different hash such as 8fefa85 and I install a qt package into my nix-env from a nixpkgs repository at a newer hash such as e4913c2, this error occurs too. So it seems you need to have compatible "environments" as well. This happened in #27790 |
This is a show stopper for me. I need VirtualBox. I hope someone has already found a solution. |
There must be a plugin which was built with old Qt version.
Showing the first few lines of stack trace here will be very helpful to find the broken plugin. |
I get:
|
ebzzry, Emm... I think Virtual Box disabled coredump. Are there any option to enable it? Anyway, you may try something like |
@LionNatsu wpa_gui works |
Even when I managed to make virtualbox works and after I've updated my environment, I still had the same problem with other application like telegram-desktop that is in my user environment. telegram-desktop
Cannot mix incompatible Qt library (version 0x50902) with this library (version 0x50901)
[1] 4213 abort telegram-desktop It seems that the I found a workaround: uninstall and re-install the package: nix-env -e telegram-desktop
nix-env -i telegram-desktop @ebzzry Did you try to uninstall and reinstall virtualbox? |
@mickours Yes, I have tried that, too. I have even “cleaned” |
@Pneumaticat says that |
I have tried that numerous times, but it didn't work with me. |
@ebzzry Looking at your You won't have to do this if you could make these two commands output the same (or make the second one output
|
strace.txt
I get the output in the attached file. I have The output of
is
|
Yeah, I've amended my comment, you should remove your user environment from the PATH (probably |
@orivej Thanks, it fixed it for the meantime! |
This bug is caused by this patch: ttuegel/qtbase@efad454 . It works only when there is exactly one copy of Qt 5.9 in PATH (by looking at |
VirtualBox runs fine now. However, I can no longer run Telegram.
|
Your nix-env -f '<nixpkgs>' -p $HOME/tdesktop -iA tdesktop
PATH=$HOME/tdesktop/bin telegram-desktop |
Thanks @orivej! |
This error can be reproduced with
Reproduce with |
I'm getting these errors when starting KDE, so I'm not even able to start the DE. these paths will be fetched (0.06 MiB download, 0.31 MiB unpacked):
|
Think I found my issue. Started uninstalling every GUI thing I installed using nix-env, and found I had xmonad++ installed there. My guess is this broke my system, but I uninstalled it together with a bunch of other packages. |
For me it was |
A few days ago, I messed with
The 'fix' for these have been installing it via |
Dupe of #37864 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/cannot-mix-incompatible-qt-library/31313/1 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/cannot-mix-incompatible-qt-library/31313/3 |
Issue description
In certain (mixed 17.09/unstable) setups, when both qt-5.9.2 and qt-5.9.1 are present, tools like VirtualBox or wpa_gui can't start and fail with this error:
This might be related to the fact that the recent update to 5.9.2 that still keeps qtwebkit at 5.9.1 (since qtwebkit-5.9.2 is not available):
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/qt-5/5.9/srcs.nix#L285-L300
Steps to reproduce
On 17.09, install dropbox from the unstable channel. wpa_gui and VirtualBox from stable will exhibit the error.
Technical details
cc/ht @woffs
The text was updated successfully, but these errors were encountered: