Issue metadata
Sign in to add a comment
|
centos7 SIGILL when run without abattis-cantarell-fonts
Reported by
randall....@gmail.com,
Dec 22 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Setup environment as described in further description. 2. Run `Xvfb :0 &`. 3. Run the chrome executable. Not exactly the nicest reproduction steps ever, but that's all I've got to work with. What is the expected behavior? It wasn't crashing before now, so I suppose that's how it's supposed to behave. What went wrong? Running google-chrome-stable (from official repos) in a VirtualBox guest. Using minimal packages and Xvfb to run "headless". For some reason, when the package "abattis-cantarell-fonts" isn't installed, the `chrome` binary triggers SIGILL. I can't find any logs on the system related to the crash in `~/.config/google-chrome`, but I'm not sure if I should be looking elsewhere. Host: * Windows 7 Enterprise SP1 x64 * Intel(R) Core(TM) i7-5600U CPU * VirtualBox 5.1.10 Guest: * Vagrantfile bento/centos-7.2 - UNMODIFIED * `sudo yum update -y` * CentOS Linux release 7.3.1611 (Core) --- > Xvfb :0 & > export DISPLAY=:0 > gdb ./chrome >> r [no debug symbols - omitting GDB output] Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Program received signal SIGILL, Illegal instruction. -- Running `sudo yum install abattis-cantarell-fonts -y` causes the above command to work correctly without crashing or encountering SIGILL. Unfortunately, I'm new to the Chromium development ecosystem, so I don't have a Chromium build or debug symbols. I checked the memory mappings in /proc and it looks like the illegal instruction is coming from within the `chrome` binary. When I update to google-chrome-unstable (57.0.2950.4) the issue still occurs. Did this work before? Yes 54.0.2840.100 Chrome version: 55.0.2883.87 Channel: stable OS Version: CentOS Linux release 7.3.1611 (Core) Flash Version:
,
Jan 18 2017
Closing with same reasoning as in https://bugs.chromium.org/p/chromium/issues/detail?id=648870#c11
,
Jan 18 2017
Not supporting the fonts the user has installed is one thing. Not telling the user why Chromium refuses to start is quite another. Instead of simply crashing on startup, please display an error message telling users that they need to install an external font package, preferably recommending one. I still have no idea what package can be installed to restore normal functionality. The workarounds in these bugs only restore most characters. Most diacritics are still missing.
,
Jan 18 2017
The original report is about 'Using minimal packages and Xvfb to run "headless".'. This description indicates that standard distribution font packages have been removed. The suggestion to improve the error message when no default font is found is welcome. Further than that we cannot provide support for such a non-standard font configuration. The link in #2 explains steps to double check your fontconfig configuration and Chrome preferences to select available fonts. For fonts with wide diacritics support, I recommend browsing the font packages of your Linux distribution and comparing the minimal setup to the standard setup. For a font with wide Unicode and diacritics support, you may also consider installing Noto fonts: https://www.google.com/get/noto/
,
Jan 18 2017
Would it be worthwhile to open a separate ticket for "display an error message when no fonts are present"? Not a developer personally, but I feel like crashing on "Illegal instruction" isn't necessarily the best mode of action for missing fonts.
,
Jan 18 2017
Filed as issue 682257 . |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Dec 26 2016