-
Notifications
You must be signed in to change notification settings - Fork 9
hawaii-session -m nested doesn't work #145
Comments
I will likely have time to take a look after I pushed the stuff I'm working on which requires doing some full screen shell work anyways. |
I'm implementing #119 these days so this will be fixed as well. |
I have tested this with the new hawaii and greenisland patches. It still seems like it doesn't display anything on a weston --shell=fullscreen-shell (or hawaii-session -m nested). unless I am missing an argument, or environment variable? EDIT: Figured more things out, |
just tested: if I do |
Of course I have tested this on Xorg all the time :( |
For the record when running hawaii-session -m nested it runs weston with fullscreen shell automatically but the hawaii process crashes. |
Thanks for looking into this. To answer your question you asked on IRC, I do support the framebuffer in my distro. |
Framebuffer: it used to support it back in 2012 with the original eglfs that was quiet different from the version I have forked to become the greenisland QPA plugin. I had it running on VirtualBox patching Mesa to add a fbdev backend took from Mer. I'm not sure whether it is avalable officially nowadays. |
As a reference: this might be related to this weston bug https://bugs.freedesktop.org/show_bug.cgi?id=93514 |
The old _wl_fullscreen_shell has been replaced with zwp_fullscreen_shell_v1 from wayland-protocols but I can't test because my weston supports only the former. Commit: 5727fde |
From IRC: now it shows something but crashes |
More stacktraces with WAYLAND_DEBUG=client http://pastebin.com/JrdmDxed |
Is this fixed with latest Weston? |
still getting a crash. the stack trace seems different though... |
|
I think it might be due to issues with greenisland not working on Weston's fullscreen-shell anymore, as manually calling the host Weston server, and calling hawaii on it results in a blank Weston screen, same as running
hawaii-sesion -m nested
Thanks
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: