https://bugs.kde.org/show_bug.cgi?id=505666
--- Comment #4 from [email protected] --- (In reply to vortex from comment #3) > (In reply to Tuomas Nurmi from comment #1) > > Thank you for the report! The debug output doesn't immediately reveal any > > obvious cause for the crash. Could you get a backtrace of the crash? (Not an > > expert in flatpak debugging, but should be possible by e.g. following > > https://docs.flatpak.org/en/latest/debugging.html , something like : flatpak > > run --command=sh --devel --filesystem=$(pwd) amarok and gdb > > /app/bin/<application-binary>) > > Oh ha, thank you for the link. Didn't knew debugging could be this easy! I > attached the gdb output as a log file to not spam the comments here. > Actually not sure what to make out of it maybe you have a clue but it seems > to be related to EGL. Which then leads to maybe nVidia? > > > qt.qpa.wayland: Could not create EGL surface (EGL error 0x3003) > > QQuickWidget: Failed to make context current when creating FBO > > qt.qpa.wayland: Could not create EGL surface (EGL error 0x3003) > > QQuickWidget: Cannot render due to failing makeCurrent() > > The Wayland connection experienced a fatal error: Protokollfehler > > I have the proprietary driver 570.196 as Amarok seems to use Qt5 and I > remember Qt5 on Walyand + nVidia being a bit ... flunky? I suppose this > issue will not be fixable unless Amarok moves to Qt6? > > By revoking Wayland access to the Amarok flatpak via flatseal and make it > run via XWayland Amarok works just fine. Sorry typo: 570.169 -- You are receiving this mail because: You are watching all bug changes.
