-
Notifications
You must be signed in to change notification settings - Fork 12
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
Minibrowser not work #7
Comments
Can you please tell me which configuration u used ? |
raspberrypi3_wpe_defconfig |
@munezbn Are you willing to look at this? That would be most helpful, if you have time. |
Yes, i don't find minibrowser... |
@dginu85 what do you mean by you dont find minibrowser ? search in usr/libexec/wpe- dir |
I try to find / -name Minibrowser |
@dginu85 @aperezdc I tried raspberrypi3_wpe_defconfig backend and faced same issue. I was getting an error saying XDG_RUNTIME_DIR not set. Even After setting it to some dir I got same error. Then I realized that there is no compositor installed so i enabled Weston/Fbdev but i was not able to launch weston.. I was wondering if anyone has tried FDO backend with wayland before ? And which compositor was used ? |
Sorry this not work.. |
@dginu85 can you please
|
I can confirm that this issue exists, I am unable to launch the MiniBrowser, or Cog for that matter. Minibrowser reports "Failed to create WPE Backend" With Cog, I get the following: (cog:648): Cog-ERROR **: 13:58:32.044: Could not instantiate any WPE backend. |
For the record, I am able to run Weston just fine using: When I try to launch MiniBrowser from within a Weston Terminal, I get "segmentation fault". |
@medemi68 To run Cog under a Wayland compositor (like Weston) you need to the
Please make sure that you are passing it, and let us know whether it works for you. |
Hi, Despite using that, I still get the same segmentation fault issue.
|
Running cog without weston gives me the following error:
|
@medemi68 The FDO backend will not work without a Wayland compositor. When you tried to run with Weston, did the shell where you ran Cog have the |
After using wpebackend-rdk , I decided to move to wpebackend-fdo. export WAYLAND_DIPLSAY=wpe Then tried both Not sure if this issue is only in the buildroot overlay or in upstream buildroot ( Have not tried yet) @aperezdc How are you launching compositor and browser ? Is it working fine for you ? |
Same here. I launch weston, withe fbdev backend:
then try to launch MiniBrowser and get nothing useful on the graphics screen and this error on the cli:
I can launch luakit in weston with this setup, but not MiniBrowser. |
That warning highlights a WebKit MiniBrowser bug. MiniBrowser is not able to handle SHM buffers yet... |
Philn, Whats the alternate approach to start WPE browser on ubuntu?. i am also getting this following warning message ** (MiniBrowser:127436): WARNING **: 09:09:33.548: WindowViewBackend: cannot yet handle wpe_fdo_shm_exported_buffer. |
Cog :) |
How test it?
#./MiniBrowser
** (MiniBrowser:241): WARNING **: 18:14:21.612: Failed to create WPE view backend
The text was updated successfully, but these errors were encountered: