New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 620183 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Unable to start Google Chrome 51.0.2704.84 on Ubuntu 14.04.4 64 bit

Reported by bhatnaga...@gmail.com, Jun 15 2016

Issue description

Chrome Version (from the about:version page): 51.0.2704.84
Is this the most recent version: Yes
OS + version: 14.04.4
CPU architecture (32-bit / 64-bit): 64 bit 
Window manager:
URLs (if relevant):
Behavior in Linux Firefox:
Behavior in Windows Chrome (if you have access to it):

What steps will reproduce the problem?
(1)  I have installed Ubuntu VM on Windows 7 host with Vagrant and Virtualbox as provider. Virtualbox Version: v5.0.20 r106931
(2)
(3)

What is the expected result?


What happens instead?

Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".
[24235:24235:0614/165259:ERROR:desktop_window_tree_host_x11.cc(891)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)

Xvfb is running on :10. Without --disable-gpu option following errors gets added
libGL error: failed to load driver: swrast
[24356:24386:0614/165638:ERROR:browser_gpu_channel_host_factory.cc(119)] Failed to launch GPU process.

Upon export LIBGL_DEBUG=verbose and running google-chrome following are the errors:
Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".
[24466:24466:0614/165839:ERROR:desktop_window_tree_host_x11.cc(891)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)
libGL: screen 0 does not appear to be DRI3 capable
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
libGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL error: failed to load driver: swrast
libGL: screen 1 does not appear to be DRI3 capable
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
libGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
[24466:24495:0614/165839:ERROR:browser_gpu_channel_host_factory.cc(119)] Failed to launch GPU process.


Please provide any additional information below. Attach a screenshot
and backtrace if possible.

 
I see same errors when I use Amazon EC2 Ubuntu VM
Are you trying to run Chrome as root? Please don't. Try again as a regular user.
Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Same error while running as regular user. File attached.
ChromeIssue.PNG
48.9 KB View Download
Does passing --disable-gpu make a difference? Does Ubuntu's Chromium browser work?
--disable-gpu option removes all the errors except Xlib:  extension "RANDR" missing on display ":10" and the process hangs.....I ran

vagrant@devvm2:/apps$ google-chrome --disable-gpu http://www.google.com
Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".

and its just sitting there, doing nothing. I will install chromium now and respond back with results/screenshots.

Same with chromium browser.

vagrant@devvm2:/apps$ chromium-browser --disable-gpu http://www.google.com
Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".
Xlib:  extension "RANDR" missing on display ":10".

Attached terminal logs when ran chromium without --disable-gpu option.
ChromiumIssue.PNG
88.0 KB View Download
Since you see this with Ubuntu's chromium-browser as well, can you try running it in gdb, when you get the hang / crash, get a backtrace. https://wiki.ubuntu.com/Chromium/Debugging

Also note: you can copy and paste the text from the terminal and attach it as a 2 KB text file instead of a 88 KB screenshot.
Project Member

Comment 10 by sheriffbot@chromium.org, Jun 16 2016

Labels: -Needs-Feedback Needs-Review
Owner: tkonch...@chromium.org
Thank you for providing more feedback. Adding requester "tkonchada@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Attached backtrace. Process hung at [30011:30036:0616/154430:ERROR:browser_gpu_channel_host_factory.cc(120)] Failed to launch GPU process.
after which I pressed Ctrl+C to move forward.
gdb-chromium.txt
45.1 KB View Download
Owner: ----
Looks like all the threads are just hanging around, twiddling their thumbs. BTW, are you trying to run Chromium over X forwarding?
I am running Xvfb as
Xvfb :10 -noreset -ac -screen 1 1366x768x24 &
and I do export DISPLAY=:10 before running chromium command.
Guys, any suggestions??
Guys, any suggestions??

Comment 16 by ajha@chromium.org, Jul 1 2016

Labels: Te-NeedsFurtherTriage
Could anyone from the Dev team help in debugging this further.
Components: Internals>GPU
Labels: -Needs-Review
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
Labels: Needs-Feedback
Sorry for the lack of progress on this issue.  Is this still reproducible in more recent versions of Chrome?
Cc: piman@chromium.org
piman@ any ideas about this issue?

Comment 21 by piman@chromium.org, Jun 27 2017

Looks like a bad driver. IIRC we blacklisted the VirtualBox driver a little while ago because it was crashing. Does this still repro?
Status: WontFix (was: Unconfirmed)
Closing due to lack of feedback.

Sign in to add a comment