1. What does "not work" mean here? Does Chromium not even launch, or does it start but not hardware accelerated? If the former, does dropping the flags (--enable-features=VaapiVideoDecoder etc.) makes it launch?
> I remember in previouse snap it is working, but withtout vaapivideodecoder working. It is another problem, ...
2. So, in previous versions of the snap, Chromium would launch, but without hardware acceleration, correct me if I understand wrong.
> ... but the wayland is sure working.
3. You mean that snap is supposed to work under Wayland, not that Wayland itself works, right?
4. I'm also interested in your `snap run --shell chromium`, `vainfo` output under Wayland.
> does wayland mode conflict with vaapivdideodecoder feature ?
I, for one, could get hardware acceleration in Chromium under Wayland working with `chromium --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland`.
Wait,
> chrome: //flags/ #ozone- platform- hint , not work.
1. What does "not work" mean here? Does Chromium not even launch, or does it start but not hardware accelerated? If the former, does dropping the flags (--enable- features= VaapiVideoDecod er etc.) makes it launch?
> I remember in previouse snap it is working, but withtout vaapivideodecoder working. It is another problem, ...
2. So, in previous versions of the snap, Chromium would launch, but without hardware acceleration, correct me if I understand wrong.
> ... but the wayland is sure working.
3. You mean that snap is supposed to work under Wayland, not that Wayland itself works, right?
4. I'm also interested in your `snap run --shell chromium`, `vainfo` output under Wayland.
> does wayland mode conflict with vaapivdideodecoder feature ?
I, for one, could get hardware acceleration in Chromium under Wayland working with `chromium --enable- features= VaapiVideoDecod er --disable- features= UseChromeOSDire ctVideoDecoder --ozone- platform= wayland` .