-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LVGL Wayland driver works with Wayland 9.0.0 but not 10.0.2 #264
Comments
With Weston 10.0.2, you should use XDG Shell, the WL SHELL is deprecated in favor of XDG Shell now! In lv_drv_conf.h, enable the macro 'LV_WAYLAND_XDG_SHELL' |
Thank you for the answer. I do believe that is the problem. I am now trying to enable XDG Shell in Yocto since the last official version of lv_drivers for Bitbake was version 8.3.0. It seems to have trouble compiling with XDG Shell enabled. |
Hi @symfund - Have you been able to use the Wayland LVGL drivers with Weston 11.0.1? I was able to build this with Yocto and deploy to my ARM32 board with Weston 11.0.1 running. Chromium is able to render on using Weston, however the lvl driver does not seem to be able to render onto the display. It does not display any errors and does not set fault, it just does not render. I can see from the Weston side debugging that LVGL is able to communicate with it. Here is the Wayland debugging I have captured from my LVGL application side ( and the source code is below ):
|
This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm facing similar Segmentation fault issue. Do we have any fix for this issue ? |
I'm using the latest version of LVGL from the master branch and the latest Wayland driver from this lv_drivers repository on a small Embedded Linux device. When I run my application again Weston 9.0.0 on my device, it works great - however, when I install Weston 10.0.2, I get a segmentation fault in the Wayland driver at the lv_obj_set_style_bg_color line. Chromium works against both Wayland versions on the same hardware. The application is communicating with Weston because I can see output by exporting the WAYLAND_DEBUG=1 environment variable.
Here is my simple example application:
Here is the output from Weston with WAYLAND_DEBUG=1 exported:
And here is the output of my application ( including the segmentation fault ):
I do not understand what is failing and why it would work with Weston 9.0.0 but not 10.0.2. I'd greatly appreciate any help!
The text was updated successfully, but these errors were encountered: