https://bugs.kde.org/show_bug.cgi?id=502148
--- Comment #2 from Claire <accou...@chapien.net> --- (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. -- You are receiving this mail because: You are watching all bug changes.
