Invisible Window Created With eglSwapBuffers Error 0x300d
-
Recently while porting a piece of software to Qt6 from Qt5 I've run into a strange issue. When trying to open a window the window does not appear, but the task bar on the bottom of the screen (I'm using KDE Plasma 6 on Wayland) does show it exists, albeit with an empty preview as though it were invisible. In the console I have the following error:
[2024-09-12T10:21:30](unknown:0) - eglSwapBuffers failed with 0x300d, surface: 0x0If I close the window via the task bar and then re-open the same element then it works perfectly. Furthermore, if I run this code in the GNU Debugger to see where exactly this error comes up, breaking at the click of the button that's supposed to open the window and stepping through all the lines of code for the window to appear, the problem does not reproduce. However, I do know by continuing the program after the callback function (a slot connected to the signal of when a button is pressed) and then continuing the program, that the error appears somewhere in the Qt event handling, likely due to a delayed revealing of the window.
The window is programmed in QML and imported into a
QQuickWidgetclass via thesetSource()function. I'm developing on a Linux desktop system (which is the target platform) running Qt 6.7.2 -
Recently while porting a piece of software to Qt6 from Qt5 I've run into a strange issue. When trying to open a window the window does not appear, but the task bar on the bottom of the screen (I'm using KDE Plasma 6 on Wayland) does show it exists, albeit with an empty preview as though it were invisible. In the console I have the following error:
[2024-09-12T10:21:30](unknown:0) - eglSwapBuffers failed with 0x300d, surface: 0x0If I close the window via the task bar and then re-open the same element then it works perfectly. Furthermore, if I run this code in the GNU Debugger to see where exactly this error comes up, breaking at the click of the button that's supposed to open the window and stepping through all the lines of code for the window to appear, the problem does not reproduce. However, I do know by continuing the program after the callback function (a slot connected to the signal of when a button is pressed) and then continuing the program, that the error appears somewhere in the Qt event handling, likely due to a delayed revealing of the window.
The window is programmed in QML and imported into a
QQuickWidgetclass via thesetSource()function. I'm developing on a Linux desktop system (which is the target platform) running Qt 6.7.2@nortega
Quite outside my area, but there are a few hits foreglSwapBuffers failed with 0x300d. Does KDE Plasma systemsettings fails to start on wayland show others are getting the same/give a clue? Or even https://forum.qt.io/topic/104421/qtquick-app-with-underlying-egl-returns-a-0x300d-egl_bad_surface-when-swapping-buffers? Or https://bugs.kde.org/show_bug.cgi?id=455913 (do you have NVidia driver)? If you are able to run your KDE under xcb instead of wayland does that make a difference? -
@nortega
Quite outside my area, but there are a few hits foreglSwapBuffers failed with 0x300d. Does KDE Plasma systemsettings fails to start on wayland show others are getting the same/give a clue? Or even https://forum.qt.io/topic/104421/qtquick-app-with-underlying-egl-returns-a-0x300d-egl_bad_surface-when-swapping-buffers? Or https://bugs.kde.org/show_bug.cgi?id=455913 (do you have NVidia driver)? If you are able to run your KDE under xcb instead of wayland does that make a difference?@JonB said in Invisible Window Created With eglSwapBuffers Error 0x300d:
@nortega
Quite outside my area, but there are a few hits foreglSwapBuffers failed with 0x300d. Does KDE Plasma systemsettings fails to start on wayland show others are getting the same/give a clue? Or even https://forum.qt.io/topic/104421/qtquick-app-with-underlying-egl-returns-a-0x300d-egl_bad_surface-when-swapping-buffers? Or https://bugs.kde.org/show_bug.cgi?id=455913 (do you have NVidia driver)? If you are able to run your KDE under xcb instead of wayland does that make a difference?The error seems to be the same as was in that ArchLinux post, as indeed I get the same error in the console (
eglSwapBuffers failed with 0x300d) as in my program. Unfortunately the post doesn't seem to be resolved, and I've tried installing bothegl-waylandandegl-wayland-gitand neither seem to work. It is possible that this is an issue with ArchLinux (or in my case, Manjaro).As for running KDE with X11 versus Wayland, I tried that and it does not cause any issues, so this is clearly a Wayland-specific issue.
If you don't mind, I'll keep the issue open a little while longer until I can definitively say what the issue is. I'll follow up and then close the issue. Thanks!
-
@JonB said in Invisible Window Created With eglSwapBuffers Error 0x300d:
@nortega
Quite outside my area, but there are a few hits foreglSwapBuffers failed with 0x300d. Does KDE Plasma systemsettings fails to start on wayland show others are getting the same/give a clue? Or even https://forum.qt.io/topic/104421/qtquick-app-with-underlying-egl-returns-a-0x300d-egl_bad_surface-when-swapping-buffers? Or https://bugs.kde.org/show_bug.cgi?id=455913 (do you have NVidia driver)? If you are able to run your KDE under xcb instead of wayland does that make a difference?The error seems to be the same as was in that ArchLinux post, as indeed I get the same error in the console (
eglSwapBuffers failed with 0x300d) as in my program. Unfortunately the post doesn't seem to be resolved, and I've tried installing bothegl-waylandandegl-wayland-gitand neither seem to work. It is possible that this is an issue with ArchLinux (or in my case, Manjaro).As for running KDE with X11 versus Wayland, I tried that and it does not cause any issues, so this is clearly a Wayland-specific issue.
If you don't mind, I'll keep the issue open a little while longer until I can definitively say what the issue is. I'll follow up and then close the issue. Thanks!
