zaps166
[24 Sep 2025 07:32:30.305] QMPlay2 crashed (SIGSEGV)
Dear friends!
QMPL2 cannot start.
Operating Environment: Windows 10 x64 19044 QMPlay2-Win64-25.09.11-portable.7z
QMPlay2 doesn't store any backtrace when it crashes, I need detailed info when it stopped to work, your hardware configuration and custom QMPlay2 configuration. Does it help when you delete all package, download again and unpack and start again?
Reproduction Steps:
- Redownload QMPlay2-Win64-25.09.11-portable.7z
- Extract to the specified directory.
- After deleting all files in the settings directory, attempt to restart QMPL. It fails to launch, with crash information logged in the log file.
My PC environment information is as follows:
- Windows 10 19044 x64
- CPU i5 3210
- Memory 8G
- Graphics card: 4.1. Intel Integrated Graphics 4000 4.2. NVIDIA: GT610
- Western Digital mechanical hard drive 5400 rpm
Try this INI file and let me know (replace existing file within portable QMPlay2 directory with this): QMPlay2.ini.zip
Does it work or still crashes?
still crashes
What if you put Renderer=legacy instead of Renderer=opengl?
[05 Dec 2024 11:18:07.318] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [05 Dec 2024 12:33:39.553] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [05 Dec 2024 19:25:52.992] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [05 Dec 2024 19:26:46.572] Unable to open: YouTube://{https://www.youtube.com/watch?v=7dE0Gvsoiu} [05 Dec 2024 19:27:24.789] QProcess: Destroyed while process ("D:\Program Files (x86)\QMPlay2\QMPlay2Player\settings\yt-dlp.exe") is still running. [05 Dec 2024 19:27:24.807] Unable to open: YouTube://{https://www.youtube.com/watch?v=7dE0Gvsoiu} [05 Dec 2024 21:41:16.776] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 00:17:57.638] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 00:19:32.364] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 00:19:55.486] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 00:21:56.003] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 00:50:17.659] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 06:09:24.558] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 11:33:28.698] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [06 Dec 2024 12:52:50.873] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed [25 Sep 2025 07:26:31.441] QMPlay2 crashed (SIGSEGV)
I completely deleted the new version of the setting and used the old version of the setting, and the above error occurred.
crashes https://github.com/zaps166/QMPlay2/releases/download/25.09.03/QMPlay2-Win64-25.09.03-portable.7z https://github.com/zaps166/QMPlay2/releases/download/25.09.11/QMPlay2-Win64-25.09.11-portable.7z
works https://github.com/zaps166/QMPlay2/releases/download/25.06.27/QMPlay2-Win64-25.06.27-portable.7z
FWIW, the latest QMPlay2 build still works for me under Win10 on an Acer Aspire One (766, I think) netbook, with OpenGL rendering of course.
That nvidia card doesn't support Vulkan from what I can tell (https://forums.developer.nvidia.com/t/gt-610-support-for-vulkan/41471) and the embedded GPU very likely doesn't either.
[06 Dec 2024 12:52:50.873] Vulkan is unable to work with QMPlay2 on this platform: Failed to load vulkan library!: ErrorInitializationFailed
This can be ignored. If you manually select OpenGL, this warning will not show anymore.
Hmm, I have to check what has been changed. If you specify legacy renderer in config file and it still crashes, most likely it's unrelated to Vulkan (need to check it). In this case QMPlay2 should not load Vulkan library.
25.06.27 -> 25.09.03 - no changes in Qt and compiler, so it's a bit weird that it crashes. Maybe other 3rd party libraries? Or this https://github.com/zaps166/QMPlay2/commit/54d4b10f061dfe7117f1fc371588d6c1e35915d2 - maybe it loads regarless of INI settings.
The old version's settings were based on the following configuration. https://github.com/zaps166/QMPlay2/releases/download/24.12.28/QMPlay2-Win64-24.12.28-portable.7z
Btw. portable should not be used in Program Files, if you want to put it there, remove portable file or add write permissions for your user.
I don't know why it crashes, I need backtrace. QMPlay2 starts on my machine without Vulkan/OpenGL and runs fine.
Please give an example of the best storage path for the portable version configuration file.
I have a similiar issue, but the only backtrace in the log I had recieved was:
[26 Sep 2025 21:57:45.958] Cannot mix incompatible Qt library (5.15.14) with this library (5.15.15)
[26 Sep 2025 21:57:45.958] QMPlay2 has been aborted (SIGABRT)
My system
OS: Debian (trixie) Firefox version: 148.0.b2 Sound runninng (working) in system: yes
Additional informations
In my case, the crash had occured when I had clicked with the right mouse button over the playlist
I have a similiar issue, but the only backtrace in the log I had recieved was:
[26 Sep 2025 21:57:45.958] Cannot mix incompatible Qt library (5.15.14) with this library (5.15.15) [26 Sep 2025 21:57:45.958] QMPlay2 has been aborted (SIGABRT)My system
OS: Debian (trixie) Firefox version: 148.0.b2 Sound runninng (working) in system: yes
Additional informations
In my case, the crash had occured when I had clicked with the right mouse button over the playlist
AppImage?
On Friday September 26 2025 13:12:00 Michal D. wrote:
[26 Sep 2025 21:57:45.958] Cannot mix incompatible Qt library (5.15.14) with this library (5.15.15) [26 Sep 2025 21:57:45.958] QMPlay2 has been aborted (SIGABRT) ... In my case, the crash had occured when I had clicked with the right mouse button over the playlist
Yes, this must be an AppImage issue where the image is missing an optional Qt component that somehow gets called upon when you open that menu. Does it happen only with the playlist context menu?
On Friday September 26 2025 13:12:00 Michal D. wrote: [26 Sep 2025 21:57:45.958] Cannot mix incompatible Qt library (5.15.14) with this library (5.15.15) [26 Sep 2025 21:57:45.958] QMPlay2 has been aborted (SIGABRT) ... In my case, the crash had occured when I had clicked with the right mouse button over the playlist Yes, this must be an AppImage issue where the image is missing an optional Qt component that somehow gets called upon when you open that menu. Does it happen only with the playlist context menu?
Your issue is unrelated to this bug report.
I don't know why it doesn't work for you, did it work in earlier versions? The AppImage runs fine on my PC.
Your issue is unrelated to this bug report.
Indeed.
I don't know why it doesn't work for you, did it work in earlier versions? The AppImage runs fine on my PC.
I suspect that this is due to the widget theme in use. But if so, it should happen with all menus (or all context/popup menus).
Your issue is unrelated to this bug report. Indeed. I don't know why it doesn't work for you, did it work in earlier versions? The AppImage runs fine on my PC. I suspect that this is due to the widget theme in use. But if so, it should happen with all menus (or all context/popup menus).
Maybe, but Qt from AppImage should not use system theme, hmm... Maybe set Fusion style for QMPlay2?
On Friday September 26 2025 14:40:38 Błażej Szczygieł wrote:
Maybe, but Qt from AppImage should not use system theme, hmm... Maybe set Fusion style for QMPlay2?
Are you certain about that? An AppImage is not sandboxed like a flatpak container.
In my case, the crash had occured when I had clicked with the right mouse button over the playlist Yes, this must be an AppImage issue where the image is missing an optional Qt component that somehow gets called upon when you open that menu. Does it happen only with the playlist context menu?
yes, it's a AppImage with was downloaded from GitHub (this repository) and for now I can confirm that currently it seem to be crashing only in this place (click of ight mouse button on playlist)
Your issue is unrelated to this bug report.
How it's unreleated if it crashes (in my case with "SIGABRT" instead of "SIGSEV")
I don't know why it doesn't work for you, did it work in earlier versions? The AppImage runs fine on my PC.
I assume that the issue may be releated to a QT version conflict.
Possible fix"
If the player would check only if QT is present instead of additionally it's version then the problem mau stop to exist 🤔
On Saturday September 27 2025 01:53:40 Michal D. wrote:
Your issue is unrelated to this bug report.
How it's unreleated if it crashes (in my case with "SIGABRT" instead of "SIGSEV")
First, you are not experiencing a crash, but an abort. The effect appears the same to the user, but the cause is very different (an abort is a decision by the software itself, a crash isn't). And that aside, even if you did get a crash because of a segmentation violation that wouldn't mean your issue is the same as the issue reported by the OP.
I assume that the issue may be releated to a QT version conflict.
Yes, that's what the error message says. An older version of a Qt component gets loaded from the OS because it is not included in the AppImage.
BTW: Qt, not QT. The latter stands for Apple QuickTime...
Possible fix"
If the player would check only if QT is present instead of additionally it's version then the problem mau stop to exist 🤔
Lol, the version check is done by Qt itself, because they guarantee backward but not forward compatibility. MAYBE the check is superfluous here, or maybe you would get an actual crash if they skipped the version check.
It is possible to figure which Qt component is the "culprit" here, but I have a feeling that's not going to be easy. Either way you'd have to file a dedicated ticket for that.
Try QT_STYLE_OVERRIDE= QT_QPA_PLATFORMTHEME= ./QMPlay2-25.09.11-1-x86_64.AppImage?
@zaps166 This hasn't happened to me before, but it happened as follows:
- The app image is minimized to the Mate desktop panel.
- I control playback with keyboard shortcuts: Windows key and arrow keys.
- While playing an MP3 file, I skip to the previous item in the playlist using the shortcuts, and it closes.❌ The previous item is a video.
- The problem doesn't appear in the program window.✅
[01 oct. 2025 04:16:26.171] Using OpenGL instead of Vulkan software rasterizer
[01 oct. 2025 04:52:51.746] QMPlay2 crashed (SIGSEGV)
[01 oct. 2025 04:53:33.987] Using OpenGL instead of Vulkan software rasterizer
[01 oct. 2025 05:02:04.256] QMPlay2 crashed (SIGSEGV)
[01 oct. 2025 05:02:14.789] Using OpenGL instead of Vulkan software rasterizer
[01 oct. 2025 05:02:28.837] QMPlay2 crashed (SIGSEGV)
[01 oct. 2025 05:02:36.998] Using OpenGL instead of Vulkan software rasterizer
@zaps166 This hasn't happened to me before, but it happened as follows:
1. The app image is minimized to the Mate desktop panel. 2. I control playback with keyboard shortcuts: Windows key and arrow keys. 3. While playing an MP3 file, I skip to the previous item in the playlist using the shortcuts, and it closes.❌ The previous item is a video. 4. The problem doesn't appear in the program window.✅[01 oct. 2025 04:16:26.171] Using OpenGL instead of Vulkan software rasterizer [01 oct. 2025 04:52:51.746] QMPlay2 crashed (SIGSEGV) [01 oct. 2025 04:53:33.987] Using OpenGL instead of Vulkan software rasterizer [01 oct. 2025 05:02:04.256] QMPlay2 crashed (SIGSEGV) [01 oct. 2025 05:02:14.789] Using OpenGL instead of Vulkan software rasterizer [01 oct. 2025 05:02:28.837] QMPlay2 crashed (SIGSEGV) [01 oct. 2025 05:02:36.998] Using OpenGL instead of Vulkan software rasterizer
Another unrelated issue.
I can't reproduce any of this crashes, without debug build and backtrace I can't do anything.
On Wednesday October 01 2025 11:26:44 Błażej Szczygieł wrote:
Another unrelated issue.
At least this one looks like it could have something to do with lack of Vulkan support and the fallback to OpenGL ;)
I can't reproduce any of this crashes, without debug build and backtrace I can't do anything.
I can't either, but I'm not using a Mate desktop (or rather, WM) and don't have a Vulkan software rasteriser that I'm aware of. Supposing that is what I think it is: does QMPlay2 default to Vulkan over OpenGL on such platforms too and why?
At least this one looks like it could have something to do with lack of Vulkan support and the fallback to OpenGL ;)
- no Vulkan loader DLL -> OpenGL fallback
- incompatible driver for QMPlay2 (e.g. lavapipe or missing features) or missing driver (only loaded exists) -> OpenGL fallback
- faulty loader or driver -> possible hang/crash (I can't do anything about it - user must reinstall GPU drivers or uninstall faulty Vulkan layers or switch to OpenGL in INI file if QMPlay2 can't start).
Additionally you can choose OpenGL manually and QMPlay2 will not try to load Vulkan at all.
I can't either, but I'm not using a Mate desktop (or rather, WM) and don't have a Vulkan software rasteriser that I'm aware of. Supposing that is what I think it is: does QMPlay2 default to Vulkan over OpenGL on such platforms too and why?
Mate is an X11 desktop session, it has nothing to do with Vulkan. X11 supports Vulkan, so QMPlay can use it. Vulkan SW Rasterizer is most likely Mesa's Lavapipe and no real Vulkan GPU driver - QMPlay2 detects it and fallbacks to OpenGL to use a real GPU instead of CPU "emulation".
You can use Vulkan SW rasterizer if you want (testing purpose), but by default it fallbacks to OpenGL IIRC.
Supposing that is what I think it is: does QMPlay2 default to Vulkan over OpenGL on such platforms too and why?
It always probe Vulkan by default (otherwise you don't know if you can use it, right?), if there's no Vulkan option on such platform, it fallbacks to OpenGL. If there's no OpenGL by chance, it fallbacks to legacy video outputs (XVideo, DDraw, QPainter).