New issue
Advanced search Search tips

Issue 909855 link

Starred by 2 users
Status: Duplicate
Merged: issue 855231
Owner: ----
Closed: Nov 30
Cc:
jmukthavaram@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chromium built for chromeos target fails to start

Reported by teemu.ku...@gmail.com, Nov 28 
UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0

Steps to reproduce the problem:
1. Build chromium for chromeos target following the instructions at https://chromium.googlesource.com/chromium/src/+/lkgr/docs/accessibility/chromevox_on_desktop_linux.md

2. In the source directory, start the chromium with something like: startx `pwd`/out/Cros/chrome

What is the expected behavior?
A working browser

What went wrong?
Chromium fails to start. Something happens but no graphics appear and then it crashes outputting some messages and stacks.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 70.0.3538.77  Channel: n/a
OS Version: Ubuntu 18.04
Flash Version: 

I'm a blind computer scientist who feels rather cozy in console most of the time but is still in need for a modern web browser. Therefore I've followed
the instructions at https://chromium.googlesource.com/chromium/src/+/lkgr/docs/accessibility/chromevox_on_desktop_linux.md hoping to enable
accessibility in Chromium (i.e. the ChromeVox screen reader and TTS) by building it for chromeos target. I'm running a fairly fresh install of Ubuntu 18.04. The same issue occurs with master and version 70.0.3538.77 (this is the same version installed by apt), but it doesn't occur when building without the chromeos target.
output.log
19.7 KB View Download

Comment 1 by jmukthavaram@chromium.org, Nov 29

Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback Needs-Triage-M70
Thanks for filing the issue. It would be more helpful if you provide us latest 16 digit uploaded crash id from chrome://crashes to proceed further.

Please find the attached screenshot for reference to provide crash id.
Thanks..!
latest crash id.PNG
17.6 KB View Download

Comment 2 by teemu.ku...@gmail.com, Nov 30 

Well, how am I supposed to get that ID without the GUI showing up?
Project Member

Comment 3 by sheriffbot@chromium.org, Nov 30

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by dtapu...@chromium.org, Nov 30

Mergedinto: 855231
Status: Duplicate (was: Unconfirmed)
The crash id you reported here is a duplicate of issue 898772; you reported it against 72.0.3591.0 occurring Oct 26th on a Windows machine so I think you might have uploaded the wrong crash image.

But from the log file you are actually seeing issue 855231.
►

Sign in to add a comment