14:33 S9: Mutter don't use hardware acceleration, I struggle to find any log as of why
14:34 S9: How can I determine where hardware acceleration pipeline fails?
14:36 S9: Even GLXGears throw a glx: failed to create drisw screen Error: glXCreateContext failed
14:37 MrCooper: S9: there should be something in the journal output from gnome-shell
14:37 S9: $ grep accel /home/bob/.cache/gdm/session.log libmutter-Message: 13:43:50.745: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated libmutter-Message: 13:43:50.890: Disabling DMA buffer screen sharing (not hardware accelerated)
14:51 MrCooper: there should be more relevant messages near those
15:02 S9: Haven't saw what you said after that there should be more around
15:03 S9: But I have something about atomic mode setting, not an error
15:03 S9: And he can't access keyring because it doesn't exist
15:03 S9: nor gSettings or SystemD1, for the same reason
15:03 S9: But yeah, more or less that's all before it
15:19 S9: Isn't there another place to identify what happens?
15:19 S9: On kernel logs it seems kind of fine ig
15:31 MrCooper: can you pastebin the full journal output from gnome-shell?
16:55 MrCooper: S9: looks like a Mesa or kernel driver issue most likely, which version of Mesa is it?
17:53 Lynne: was virtgpu or gfxstream enabled by default recently?
17:54 Lynne: I get a flood of "MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES" errors
18:09 digetx: gfxstream
18:09 digetx: uriah: yw
18:09 uriah: :)
18:32 Lynne: I don't have even it enabled in -Dvulkan-drivers
18:48 digetx: you shouldn't get that msg without enabled gfxstream, unless something changed very recently
18:48 digetx: anyways, it needs to be fixed