You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been struggling through getting chromium running on an iMX8MP platform and am hoping someone can point me in the right direction here. I have finally gotten chromium running on my hardware, but in the process have identified an issue with all versions in meta-browser beyond 86.0.4240.111.
I had previously seen 86.0.4240.111 working on an iMX8MM platform. I've now migrated to an iMX8MP platform and have been unable to get any version newer than 86.0.4240.111 to function on my board. Specifically, the versions I have tried are: 88.0.4324.150, 86.0.4240.198, and 86.0.4240.111.
In the failing case, the result is --
weston/wayland starts just fine. I can start weston-terminal and I get the expected terminal on-screen and keyboard input is accepted. However, when I try to run chromium via chromium --no-sandbox --in-process-gpu I get a segfault. If I run with WAYLAND_DEBUG=1, the final output lines are in reference to xdg_surface_configure with the last line specifically: [email protected]_synchronization(new id zwp_linux_surface_synchronization_v1@23, wl_surface@17 then it segfaults.
I found this thread #253 which indicates a similar issue with the resolution being "zwp linux dmabuf" is not available. What does that mean? I believe I have enabled all relevant 'dmabuf' options in my kernel config
From the functional version (86.0.4240.111), I can see the next output line should be in reference to wl_viv create_buffer, which must be what is causing the segfault on the newer versions. Would this imply a dma (hardware???) issue? I am very unsure of where to chase this next.
Here is the full WESTON_DEBUG=1 output when trying to launch:
It’d help if you can get a stack trace to understand the reason why it failed. Alternatively, you can always try the latest version of chromium as ozone/wayland is under heavy development and things can get broken and fixed later, but there might be a gap between fixes as officially chrome releases do not support wayland yet and QA doesn’t test wayland
Hi,
I have been struggling through getting chromium running on an iMX8MP platform and am hoping someone can point me in the right direction here. I have finally gotten chromium running on my hardware, but in the process have identified an issue with all versions in meta-browser beyond 86.0.4240.111.
I had previously seen 86.0.4240.111 working on an iMX8MM platform. I've now migrated to an iMX8MP platform and have been unable to get any version newer than 86.0.4240.111 to function on my board. Specifically, the versions I have tried are: 88.0.4324.150, 86.0.4240.198, and 86.0.4240.111.
In the failing case, the result is --
weston/wayland starts just fine. I can start weston-terminal and I get the expected terminal on-screen and keyboard input is accepted. However, when I try to run chromium via
chromium --no-sandbox --in-process-gpu
I get a segfault. If I run with WAYLAND_DEBUG=1, the final output lines are in reference to xdg_surface_configure with the last line specifically:[email protected]_synchronization(new id zwp_linux_surface_synchronization_v1@23, wl_surface@17
then it segfaults.I found this thread #253 which indicates a similar issue with the resolution being "zwp linux dmabuf" is not available. What does that mean? I believe I have enabled all relevant 'dmabuf' options in my kernel config
From the functional version (86.0.4240.111), I can see the next output line should be in reference to wl_viv create_buffer, which must be what is causing the segfault on the newer versions. Would this imply a dma (hardware???) issue? I am very unsure of where to chase this next.
Here is the full WESTON_DEBUG=1 output when trying to launch:
Any help on this would be greatly appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: