| Summary: | Chromium shows "Aw Snap" even for internal pages | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Laurentiu Pancescu <lpancescu> | ||||||||
| Component: | chromium | Assignee: | Tom "spot" Callaway <tcallawa> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 25 | CC: | rbu, tcallawa, yaneti | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-12-12 10:42:33 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
Created attachment 1216241 [details]
Messages printed by chromium-browser in a terminal (with debuginfo)
I installed the debug information (dnf debuginfo-install chromium) and recaptured the log. Chromium actually started without any problems the first time after installing the debug packages, but a second attempt produced the same result as decribed in the bug report. I'm not sure if the debug packages improved the stack trace, I still see <unknown> pretty much everywhere.
I'm building a new package in rawhide right now, I think it might address this issue too. Chromium takes a _long_ time to build. Also, if you're on i686, I had to do some pretty absurd stuff just to get it to build for that target. I humbly suggest you consider upgrading to x86_64. I run x86_64 on my main Fedora system, but I need it for serious work, so I'm only using official releases. I installed F25 Beta on a secondary system, only used for browsing in front of the TV (old netbook, Atom N270, only supporting i686 - the CPU has no 64-bit support). I guess i686 is on its way out... Should I try to run Chromium from F25 x86_64 live media? I could also install F25 Beta in VirtualBox. chromium-54.0.2840.90-3.fc25.i686 works without any issue for me - thanks! Created attachment 1228948 [details]
chromium-x86_64.log
I am seeing crashing tabs (even on the start/bookmark screen) with a SEGV_MAPERR as well. This is on chromium.x86_64-53.0.2785.143-1.fc24
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 1216222 [details] Messages printed by chromium-browser in a terminal Description of problem: Chromium displays just "Aw Snap" pages instead of actual web pages. Not even its internal pages for Settings or Extensions are working. Version-Release number of selected component (if applicable): chromium-54.0.2840.71-1.fc25.i686 How reproducible: Always Steps to Reproduce: 1. Start Chromium from graphical menu or terminal Actual results: Chromium displays a warning for each extension (HTTPS Everywhere, uBlock Origin, Privacy Badger) stating that it crashed. Trying to load any web page will just show an "Aw Snap" page, including internal pages like chrome://extensions and chrome://settings. Expected results: Chromium keeps working in F25 like it used to do in F24. Additional info: I started Chromium in a terminal via "chromium-browser 2>&1 | tee chromium.log" and attached the resulting log file. After starting, I clicked "Settings" in Chromium's menu, and then "Reload" in the "Aw Snap" page it displayed, then on "Send feedback", and then closed Chromium from its menu. Is there any debug package I could install to produce a more complete stack trace?