Issue metadata
Sign in to add a comment
|
content_shell fails to initialize fonts on Ubuntu 16.04 xenial and Fedora 23
Reported by
jwo...@igalia.com,
Jun 20 2016
|
||||||||||||||||||||
Issue description(After manually working around issue 621694 ) content_shell is crashing with a problem relating to fonts on Ubuntu 16.04 xenial. jwolfe@jwolfe-desktop:~/chromium/src$ /home/jwolfe/chromium/src/out/Release/content_shell --run-layout-test --enable-crash-reporter --crash-dumps-dir=/home/jwolfe/chromium/src/out/Release/crash-dumps - [12535:12535:0620/150651:358181246756:FATAL:fontconfig_util_linux.cc(77)] Check failed: FcConfigSetCurrent(FcConfigCreate()). #0 0x0000057af32e base::debug::StackTrace::StackTrace() #1 0x0000057eda9f logging::LogMessage::~LogMessage() #2 0x0000051e90e0 gfx::SetUpFontconfig() #3 0x00000574237d content::BlinkTestPlatformInitialize() #4 0x000005702f2a content::ShellMainDelegate::BasicStartupComplete() #5 0x0000042c71b3 content::ContentMainRunnerImpl::Initialize() #6 0x0000042c4b59 content::ContentMain() #7 0x000000578379 main #8 0x7fa746665830 __libc_start_main #9 0x000000578259 _start Aborted (core dumped) In case it matters, I noticed a big list of font paths in ui/gfx/test/fontconfig_util_linux.cc, and some of those paths (first 2 and last 3) do not exist on my system.
,
Jun 22 2016
,
Jun 24 2016
I am getting it 100% on Fedora 23.
,
Jun 27 2016
Does the failure go away if you comment out the paths that don't exist on your system? That would be a good way to determine if it matters. :-)
,
Jun 27 2016
Good idea. No the issue doesn't go away :( . So it doesn't seem to have anything to do with those paths.
,
Jun 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fb607474cba9881f85565dffaf924a55c6994bb5 commit fb607474cba9881f85565dffaf924a55c6994bb5 Author: thomasanderson <thomasanderson@google.com> Date: Tue Jun 28 00:27:37 2016 Fix content shell layout test failure related to Fontconfig Work around an issue that only occurs on libfontconfig.so.1.9.0 Also update a comment that's no longer accurate BUG= 621695 Review-Url: https://codereview.chromium.org/2104653002 Cr-Commit-Position: refs/heads/master@{#402342} [modify] https://crrev.com/fb607474cba9881f85565dffaf924a55c6994bb5/ui/gfx/test/fontconfig_util_linux.cc
,
Jun 28 2016
Please try running the content_shell again on ToT You probably have to manually install these packages http://launchpadlibrarian.net/107999832/ttf-kochi-gothic_20030809-15_all.deb http://launchpadlibrarian.net/107999831/ttf-kochi-mincho_20030809-15_all.deb http://launchpadlibrarian.net/162388639/ttf-indic-fonts-core_0.5.14ubuntu1_all.deb http://launchpadlibrarian.net/162388648/ttf-punjabi-fonts_0.5.14ubuntu1_all.deb And you may or may not need this as well sudo apt-get install apache2 wdiff msttcorefonts If you need to do either of the above things, please create a new bug to update install_build_deps.sh
,
Jun 28 2016
Thanks. I had to install apache2, and 3 of the 4 .deb files you linked. Installing one of the .deb files was not necessary, and didn't work anyway: $ sudo dpkg -i ~/tmp/ttf-punjabi-fonts_0.5.14ubuntu1_all.deb Selecting previously unselected package ttf-punjabi-fonts. (Reading database ... 236833 files and directories currently installed.) Preparing to unpack .../ttf-punjabi-fonts_0.5.14ubuntu1_all.deb ... Unpacking ttf-punjabi-fonts (1:0.5.14ubuntu1) ... dpkg: dependency problems prevent configuration of ttf-punjabi-fonts: fonts-guru (2:1.2) breaks ttf-punjabi-fonts (<< 2:1.0) and is installed. Version of ttf-punjabi-fonts to be configured is 1:0.5.14ubuntu1. fonts-guru-extra (2.0-3) breaks ttf-punjabi-fonts (<< 2:1.0) and is installed. Version of ttf-punjabi-fonts to be configured is 1:0.5.14ubuntu1. dpkg: error processing package ttf-punjabi-fonts (--install): dependency problems - leaving unconfigured Processing triggers for fontconfig (2.11.94-0ubuntu1) ... Errors were encountered while processing: ttf-punjabi-fonts After all that, the layout tests seem to be running successfully. I created issue 624091 as you requested.
,
Jun 28 2016
Also, as a reminder, I had to manually work around issue 621694 to get the tests to work. And then there are hundreds of failures (out of 40173 tests), but I suppose that's normal. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dpranke@chromium.org
, Jun 20 2016Owner: thomasanderson@chromium.org