-
Notifications
You must be signed in to change notification settings - Fork 434
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
OSM Maps (Default map) causes hang on load #1369
Comments
There is a Qt 5.15.3 Map bug when OSM maps are used: https://bugreports.qt.io/browse/QTBUG-103592 I presume the same problem exists in 5.15.4, that you appear to have, and unfortunately the workaround in this patch #1169 only checks for 5.15.3:
|
Changing that one line fixed it for me. Works like a charm. |
Reopened as I need to fix it for others |
Qt 5.15.2 also has this bug. I upgraded my openSUSE from LEAP 15.3 to 15.4 (latest) so I could continue to compile this project after the Qt required version changed and hit this issue (openSUSE 15.4 supplies Qt version 5.15.2). I have patch my local system but it would be nice if someone with local repository access could add Qt 5.15.2 to the two version checks. If not I can fork it and do a pull request when I get some time.
|
Well, it's not as simple as saying 5.15.2 has the problem, as this version is fine on Windows and Mac, and also Ubuntu 21.10 has Qt 5.15.2 and doesn't show the problem. And we can't use mapboxgl on Windows. |
Well that's interesting that Ubuntu's supplied Qt5.15.2 doesn't have the problem. I wonder what the difference is between there version and openSUSE's ? I will have to do some research.
|
Qt 5.15.6 has the problem on Ubuntu 22.10 beta |
Updating name as we have known about the cause for a while now |
Latest patch just uses mapboxgl on all Linux builds, as that seems safest. |
Version 7.6.0-42-g75148f965
Built from source on Debian (Sid)
Qt 5.15.4 64bit Rx 24bit Tx 16bit
HackRF One (Latest firmware)
After trying to use either the map feature or the ADS-B channel, sdrangel hangs (seemingly indefinitely)
sdrangel.log:
GDB output:
The text was updated successfully, but these errors were encountered: