Closed dee42 closed 4 years ago
To support GTK 3 you need to build CEF with GTK 3 enabled, this can be done with the automate.py script by providing --use-gtk3
flag. Also you need to patch cefpython sources with the patch that is attached in one of the comments in Issue #446.
After following the instructions above and if the issue still persists answer these two questions:
--disable-gpu
and disable-gpu-compositing
switches make any difference?Hi, thanks for this information. I recompiled with --with-gtk3 (I didn't clean, but since it rebuilt everything where the Makefile was touched this seemed unnecessary). I applied the patch from #446. I disabled compositing on my Window Manager. I passed in the disable-gpu and disable-gpu-compositing switches to cef Initialize in the wxpython example. Exact same segmentation fault and traceback.
What GTK 3 version is installed in your OS? Can you try installing version <= 3.14? Versions >= 3.15 are known to have issues with CEF (see this comment https://github.com/cztomczak/cefcapi/issues/9#issuecomment-348821478).
Unfortunately I need to work off a base of Ubuntu 18.04, which comes with GTK 3.22. Do you have a patch that gets it to work without transparency? Reading your comment, I can see that was the blocker, but I do not need transparency.
The referenced issue reports that CEF has issues with GTK 3.22 default visual in general. You can try changing the visual, there is C code available there. I can't say if that will help you resolve the issue here, but it's worth a try.
Thanks. I have fixed the issue for me by installing wxPython wheels linked to GTK2. The standard pip install ends up linked to GTK3. The wheels are available here: https://extras.wxpython.org/wxPython4/extras/linux/gtk2/ubuntu-18.04. I'm going to stop looking into this now, as that's a good enough solution for me, and it looks like next version of cefpython, when it is released, will have full GTK3 support.
Duplicate of #447.
In the wxPython example compiled with GTK3, after applying the CEF patch from #452, there is a secondary crash as soon as the main loop starts up.
The logging and traceback is as follows: