Recent searches
Search options
Olá!
I've just blogged about the recent developments in the Chromium Ozone/Wayland project, which is getting closer to officially shipping to Linux Desktop users.
Huge thanks to @igalia and our sponsors for making it possible 
#chromium #linux #wayland #igalia
#foss #opensource
https://nickdiego.dev/blog/chromium-ozone-wayland-the-last-mile-stretch/
@nickdiego @igalia awesome post!
@nickdiego @igalia Thanks, I'll try drm-sync-obj flag. I hope H/W video acceleration would be fixed on Wayland aw well.
@spyke Assuming you're a nvidia user, I'd suggest to keep an eye on https://crbug.com/343352540 and https://crbug.com/385470198 it's all experimental still, though some improvements have landed recently. Personally, I've been using chromium wayland on Gnome 48 in a nvidia setup as my daily driver for ~2y now, and it's been working pretty well and stable.
@nickdiego Thanks, Chrome is using my integrated Intel Xe. Are there plans to support Vulkan on ozone-wayland?
@spyke If it's a dual-gpu setup, have you tried with `--render-node-override=/path/to/gpu` ? It's landed recently as a short-term workaround for those setups https://crrev.com/1415765. AFAIK vulkan on linux is experimental, dunno about its status but with the correct flags and depending on the env it might work already.
@nickdiego I'll give it a try. Thanks!
@nickdiego When I grow up, want to be smart like you <3
@edrzmr hahahaa you'll have always a huge fan here 
@nickdiego @igalia So interesting! Amazing work, Nick!
@asilva thanks amigo! 
@nickdiego @igalia Great work!
Something that wasn't mentioned but is still missing is support for graphics tablet input. Is that on your radar?
@nicofee Hey! that's a good point, indeed! There seems to be some reports about it, eg: https://crbug.com/40282832, though it's not in the roadmap for the current sponsorship afaik :(
@nickdiego @igalia very nice news. This is all work that will eventually become accessible to eletron apps right?
Seems great progress 
@vascorsd Thanks! Mostly yes, there are probably a few which may require some electron-specific plumbing or hooks though.
@nickdiego @igalia mutter has basic, experimental support for the session management protocol, so any feedback (what doesn't work, what state should be restored, etc) would be appreciated when you get to it
@swick Hey Sebastian! Yeah, I'm looking at mutter's impl at this very moment 
and will hopefully have some feedback soon. thx!
@nickdiego @igalia great write up, Cheers Nick! Looks like some great things ahead and no doubt some old code to sift through.
Do you happen to know if Chromium is suffering with resize issues on compositors that don’t support server side decorations? Folks over at electron were having massive issues when using the ozone flag, so wasn’t sure if it was a them or chromium issue. Here’s the ticket if you want to take a look and have some thoughts https://github.com/electron/electron/issues/44543
@justin Hi, thanks!
Not that I'm aware of. From a quick look, the analysis in https://github.com/electron/electron/issues/44543#issuecomment-2599659491 seems in the right direction. Particularly, the `window->SetInputRegion(std::nullopt)` seems suspicious. It'd need further analysis tbh.
@nickdiego @igalia What happened to the "No native theme support in non-browser chrome widgets" bug? it redirects to the android bug tracker where it's marked as WONTFIX and appears to have no details
@migratory Whoops! Just fixed the link there: https://issues.chromium.org/396190939
Thanks!