SUMMARY When you send certain apps to the system tray that use the EGL backend on wayland, they cannot be maximized again and become stuck on the tray. Current apps does show the icon as if it has been maximized, but the window size is set to zero. When run from terminal, this is the full output: Database version 10 qrc:/qt/qml/org/kde/kasts/qml/FeedListPage.qml:18:1: QML FeedListPage: Created graphical object was not placed in the graphics scene. qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x6114e3155f00 STEPS TO REPRODUCE 1. Launch Kasts or Akgregator with EGL backend (not software) 2. Click the close button to send it to the tray 3. Try to maximize from tray. Icon appears on icons only task manager, but application cannot be maximized. 4. If running from terminal, the following is output: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x6114e3155f00 OBSERVED RESULT The program does not maximize. qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x6114e3155f00 is output as an error. EXPECTED RESULT The program is restored from the tray. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.13.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060 SUPER ADDITIONAL INFORMATION Running with QT_QUICK_BACKEND=software fixes the issue, but I imagine it would be preferable to fix this rather than work around it.
I'm not immediately able to reproduce this with kasts on git-master. Can you share the command you're using for kasts or akgregator to launch them from command line which showcases the bug? thanks.
(In reply to TraceyC from comment #1) > I'm not immediately able to reproduce this with kasts on git-master. Can you > share the command you're using for kasts or akgregator to launch them from > command line which showcases the bug? thanks. Hey, I'm just running kasts with no extra commands. QT seems to claim it's an issue with NVidia from what googling I did -- if it helps, I am using the nvidia-open-dkms driver. https://archlinux.org/packages/extra/x86_64/nvidia-open-dkms/ I realize you may not have the hardware to test if it is indeed hardware specific, so let me know if anyone on the team has an nvidia card to test with. Here is the issue being discussed on the QT forums: https://forum.qt.io/topic/158667/invisible-window-created-with-eglswapbuffers-error-0x300d. Other posts suggest that QT_QPA_PLATFORM=xcb fixes the issue too. After finding that solution, I tested it and indeed, it does work fine under XWayland. So, the information I now have for you: Under Wayland, Kasts works if Software rendering is the backend instead of hardware, but this means images won't display. Under X, the app works perfectly. This indicates that it's some sort of Wayland issue, no? I ran it from terminal with QT_QPA_PLATFORM=xcb, and interestingly, the "qrc:/qt/qml/org/kde/kasts/qml/FeedListPage.qml:18:1: QML FeedListPage: Created graphical object was not placed in the graphics scene." error still appears, but the SwapBuffer error does not. Still, as far as I can tell, the error doesn't mean anything; at least, it's not effecting anything I can notice.
Update, after a sudo pacman -Syu that updated Kwin and QML yesterday, this seems to be fixed. I'm guessing it was something on QT's end? Regardless, I still have an issue but it is more Kasts related I believe. Thank you!
Glad to hear it. Thanks for the update.