Closed hedgepigdaniel closed 5 years ago
we are definitively interested!
(ozone) [daniel@danielpc-arch src]$ CHROME_DEVEL_SANDBOX=/opt/chromium/chrome_sandbox out/OzoneWayland/chrome --mus --ozone-platform=wayland [20925:20954:0220/081905.324229:ERROR:xkb_keyboard_layout_engine.cc(694)] Not implemented reached in virtual bool ui::XkbKeyboardLayoutEngine::SetCurrentLayoutByName(const std::string &) [20925:20925:0220/081906.002839:ERROR:global_shortcut_listener_ozone.cc(26)] GlobalShortcutListenerOzone object created [20925:20925:0220/081906.002948:ERROR:global_shortcut_listener_ozone.cc(48)] Not implemented reached in virtual bool extensions::GlobalShortcutListenerOzone::RegisterAcceleratorImpl(const ui::Accelerator &) [20925:20925:0220/081906.002993:ERROR:global_shortcut_listener_ozone.cc(48)] Not implemented reached in virtual bool extensions::GlobalShortcutListenerOzone::RegisterAcceleratorImpl(const ui::Accelerator &) [20925:20925:0220/081906.003051:ERROR:global_shortcut_listener_ozone.cc(48)] Not implemented reached in virtual bool extensions::GlobalShortcutListenerOzone::RegisterAcceleratorImpl(const ui::Accelerator &) [20925:20925:0220/081906.003108:ERROR:global_shortcut_listener_ozone.cc(48)] Not implemented reached in virtual bool extensions::GlobalShortcutListenerOzone::RegisterAcceleratorImpl(const ui::Accelerator &) [20925:20925:0220/081906.373875:FATAL:visitedlink_master.h(499)] Check failed: used_count == useditems (17744 vs. 17747)
any particular step to reproduce the issue? Note that we run on top of a development snapshot, so it is possible that the bug is also unrelated to our implementation.
All I did was compile chrome
and chrome_sandbox
(the one that ended up in /opt/chromium/chrome_sandbox
with the following args (a mixture of the built bot and the readme):
use_debug_fission = true
linux_use_bundled_binutils = false
clang_use_chrome_plugins = false
treat_warnings_as_errors = false
enable_nacl = false
use_lld = false
enable_mus = true
use_jumbo_build = true
cc_wrapper = "ccache"
use_ozone = true
ozone_platform_wayland = true
ozone_platform_x11 = true
ozone_platform_headless = true
ozone_auto_platforms = false
use_xkbcommon=true
And then ran chrome as per the log.
I did not clean my profile dir first, so my older version of chromium now complains that the profile is corrupt when it starts. I assume this would not cause the new versions to crash.
Interestingly, Xwayland crashes when reconnecting my external screens after running it in some circumstances.
@hedgepigdaniel Have you tried to build using this AUR? https://aur.archlinux.org/packages/chromium-wayland-git
Maybe it give you some insight about the configs @onny used to build & run successfully this project on Arch.
I haven't but I will check it out, thanks :)
from the PKGBUILD
pkgver=48.0.2548.0
pkgver_=63.0.3239.84
I wonder what will happen when I build it...
Both pkgver version doesn't play any important role here, since the latest sources are pulled from this git repo. I just included the variables to match the original chromium PKGBUILD.
Good catch!
command line that you used to run mus_demo:
/mash --service=mus_demo --external-window-count=2 --mus --ozone-platform=wayland
Command line needed to run mus_demo:
/mash --service=mus_demo --external-window-count=2 --mus --ozone-platform=wayland --mus-hosting-viz
more explicitly: today we need both --mus and --mus-hosting-viz parameters to launch mus_demo. I will push a PR that requires you to do only --mus, as per our documentation, and so that it gets compatible with chrome and content_shell.
@onny, so this AUR does provide a build of the chromium/wayland being worked out by Igalia?
I believe then the pkgver values (48.x) if innacurate might at very least scare testers away, since it is a pretty old version of Chromium.
@hedgepigdaniel the services_unittests failure look like a hiccup on the tests.
our latest build have it running 100% fine: https://build-chromium.igalia.com/#/builders/1/builds/691/steps/25/logs/stdio
added not_confirmed flag. this should be checked with desktop_aura integration
not applicable any more.
Hello,
I've just compiled this project successfully but I came across a runtime error, and some test failures. Hopefully its useful.
chromium-ozone-wayland:
70a4f45acc4106e2010efa51cdfc74a39e163c56
Desktop env: GNOME 3.26 running wayland GPU: Intel Kaby Lake integrated graphics on a Dell XPS 9560 (Also has a second NVIDIA GTX 1050 which is not being used) Screens: Only the internal 4K screen was connected kernel: 4.15.3 OS: Arch LinuxDebug output from running chrome:
Debug output from running demo:
Debug output from running
ozone_unittests
:Debug output from running
services_unittests
: