-
Notifications
You must be signed in to change notification settings - Fork 82
Cannot run chromium! #448
Comments
I think it's because of mesa. So Wayland cannot initialize EGL. But Mesa is installed... |
@kalyankondapally , please help! I cannot run chromium :( |
[2833:2833:0119/143808:ERROR:browser_main_loop.cc(216)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. [2833:2833:0119/143810:WARNING:object_manager.cc(368)] org.bluez /: Failed to get managed objects |
@joone , can you please help? |
@vrotenberg Sorry missed this one. Can you share information about your hardware and drivers. |
We use Radeon HD 6320 and EGL r600 driver is installed in Mesa. |
I am trying to run this chromium on the regular Wayland version built from here: http://wayland.freedesktop.org/xserver.html |
@kalyankondapally, should I install another driver? |
Can you set this environment variables and share any verbose it prints out after trying to run chromium. export MESA_DEBUG=1 Also, have you tried running wayland demos ? |
The log is: [10:24:34.685] weston 1.9.90 I even installed driconfig so it has generated for me .drirc file so I don't see anymore "libGL: Can't open configuration file /home/victor/.drirc: No such file or directory" error but it didn't help. I tried to run weston-simple-egl and it worked OK. |
Hmm not sure whats happening. Did you try debugging as mentioned here |
No, it's very complicated. Maybe it need another driver - not r600? As you see it loads here: libEGL debug: DRI2: dlopen(/home/victor/install/lib/dri/r600_dri.so) r600 driver. How can I change it? Thanks. |
I don't know if that can help but I have the same issue with an amd A10-4600m apu on a fresh Arch Linux install using Wayland/Weston 1.9.0. |
Hi!
I am trying to run chromium --no-sandbox and get the error:
[30176:30176:0118/102610:ERROR:desktop_window_tree_host_ozone.cc(572)]
Not implemented reached in virtual void
views::DesktopWindowTreeHostOzone::SetWindowIcons (const gfx::ImageSkia
&, const gfx::ImageSkia &)
[30176:30176:0118/102610:ERROR:desktop_window_tree_host_ozone.cc(583)]
Not implemented reached in virtual void
views::DesktopWindowTreeHostOzone::InitModalType( ui::ModalType)
[30176:30176:0118/102610:ERROR:ozone_webui.cc(51)] Not implemented
reached in vi rtual gfx::FontRenderParams
views::OzoneWebUI::GetDefaultFontRenderParams() cons t d to start the
GPU process in software rendering mode. Software rendering is not
supported in Ozone-Wayland, so this is fatal. Usually this error occurs
because
the GPU process crashed in hardware rendering mode, often due to
failure to ini tialize EGL. To debug the GPU process, start Chrome with
--gpu-startup-dialog so
that the GPU process pauses on startup, then attach to it with 'gdb -p'
and run
the command 'signal SIGUSR1' in order to unpause it. If you have xterm
then it is easier to run 'chrome --no-sandbox --gpu-launcher='xterm
-title renderer -e g
db --eval-command=run --args''
During the build I also had the errors:
ninja: warning: multiple rules generate obj/ozone/ui/webui/webui.select_file_dialog_impl_webui.o. builds involving this target will not be correct; continuing anyway [-w dupbuild=warn]
ninja: warning: multiple rules generate obj/ozone/ui/webui/webui.ozone_webui.o. builds involving this target will not be correct; continuing anyway [-w dupbuild=warn]
ninja: warning: multiple rules generate obj/ozone/ui/webui/webui.input_method_context_impl_wayland.o. builds involving this target will not be correct; continuing anyway [-w dupbuild=warn]
Maybe because of that now I cannot run chromium?
Please help!
The text was updated successfully, but these errors were encountered: