Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1825510
Summary: | chromium: crash on startup - (autofill?) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Yanko Kaneti <yaneti> |
Component: | chromium | Assignee: | Tom "spot" Callaway <tcallawa> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | carl, tcallawa, tpopela, yaneti |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | chromium-81.0.4044.122-1.fc32 chromium-81.0.4044.122-1.fc30 chromium-81.0.4044.138-1.fc31 chromium-81.0.4044.138-1.el8 chromium-81.0.4044.138-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 02:32:18 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: | |
Embargoed: |
Description
Yanko Kaneti
2020-04-18 17:05:15 UTC
It starts OK with a new user profile i.e --user-data-dir=... That sure seems like a VAAPI issue. See: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) [67607:67607:0418/195243.088763:ERROR:vaapi_wrapper.cc(482)] vaInitialize failed: unknown libva error Does vainfo run properly on that system? Can you give me more details about the hardware, specifically, the GPU and driver? I don't think the libva errors are related to the crash. I have them (and they look the same) with the OK working 80.0.3987.163-1 and with 81.0.4044.113-1 $ vainfo libva info: VA-API version 1.6.0 libva info: Trying to open /usr/lib64/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.6 (libva 2.6.1) vainfo: Driver version: Mesa Gallium driver 19.2.8 for AMD VERDE (DRM 2.50.0, 5.5.17-200.fc31.x86_64, LLVM 9.0.0) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileNone : VAEntrypointVideoProc Okay. Do you have any extensions installed? I have a bunch of Google extensions which I can't remember explicitly installing and the Gnome shell extensions. But it doesn't seem to be extensions related because it happens with all of them removed. I tried a game of whack-a-mole in the user dir and I've narrowed it down to the "Default/Web Data" sqlite database. If I remove that the browser starts. With the broken menu I mentioned in the bodhi update, but still it starts. Apparently I have 5 autofill_profiles in that database. It crashes if the autofill_profiles table has any of them in it. Starts only if I delete all 5. FWIW chromium-freeworld-81.0.4044.92-1.fc31.x86_64 works with the existing user config without crashing, and with a proper menu (In reply to Yanko Kaneti from comment #7) > FWIW chromium-freeworld-81.0.4044.92-1.fc31.x86_64 works with the existing > user config without crashing, and with a proper menu I'm not sure what you mean by a "proper menu", but that is not the same version, so it's a bit difficult to compare. The last comment from cowboysmall on the bodhi update actually nails the problem. I hadn't even realized there was a chromium-common sub-package and I hadn't updated it while testing the build. So both the crash and the broken menu are happening with chromium-81.0.4044.113-1 alongside chromium-common-80.0.3987.163-1. Everything is cured by updating to chromium-common-81.0.4044.113-1 This bug is not a bug, but the lacking stricter inter-dependency probably should be. Yeah. I've got new builds going to fix the dependency issue now. FEDORA-2020-c461588d71 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c461588d71 FEDORA-EPEL-2020-03964ba7fd has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-03964ba7fd FEDORA-2020-5a2f7328c9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5a2f7328c9 FEDORA-2020-9fc39815b9 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9fc39815b9 FEDORA-EPEL-2020-ac596053e4 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ac596053e4 FEDORA-2020-5a2f7328c9 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-5a2f7328c9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5a2f7328c9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-72116e7775 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-72116e7775 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-324f1b735d has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-324f1b735d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-86c77554e9 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-86c77554e9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-86c77554e9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-0e7f1b663b has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0e7f1b663b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0e7f1b663b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-b82a634e27 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b82a634e27` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b82a634e27 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-b82a634e27 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-0e7f1b663b has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-03d5f14bbe has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-03d5f14bbe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-cd30b5b1cf has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-cd30b5b1cf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-da49fbb17c has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-da49fbb17c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-da49fbb17c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-da49fbb17c has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-03d5f14bbe has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-cd30b5b1cf has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |