Closed mattkae closed 5 months ago
@mattkae can you confirm this didn't happen for you on main before #3067?
@Saviq It does happen before then as well :+1:
This is better than we were in v2.15
of mir. On my system, nouveau drivers can barely render anything at all, while the proprietary drivers crash.
could this also be related to the recently touted "explicit sync" (linux-drm-syncobj-v1) support?
could this also be related to the recently touted "explicit sync" (linux-drm-syncobj-v1) support?
I am unsure, although I no longer see this. I wonder if it was just because we were selecting the graphics platform poorly in the past.
Mir doesn't support that protocol (yet), so unlikely to have impact.
I will close since I no longer see this and this issue was from very long ago
Mir doesn't support that protocol (yet), so unlikely to have impact.
should i make a separate issue for eventual support? it seems relevant for the usecases of lomiri, miraclewm and miriway
Done:
thanks!
What I ran
Result
https://github.com/MirServer/mir/assets/25062299/cdda22c5-a67d-4fcb-af3d-481ae84fdbb0
Output
Full Logs