Pretty much the title. I have been trying to pinpoint what’s causing it and the proper logs, but the only thing in common so far in all times it has happened is firefox and another xwayland application are present.

logs show several errors, including this one - but how could I file a bug report, if I don’t know how to reproduce it ?

Aug 15 17:09:37 hostname konsole[3721]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce.

  • shadowintheday2@lemmy.worldOPEnglish
    3·
    3 months ago

    Another section of the log when this happened:

    Aug 15 18:00:48 arch kwin_wayland[3328]: This plugin does not support raise()
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glBindFramebuffer(non-gen name)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)