Description of problem: Tried the chromium-81.0.4044.113-1.fc31 from updates-testing and it crashes on startup, not sure where exactly.. ''' $ chromium-browser [67577:67577:0418/195242.837813:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id ATTENTION: default value of option allow_rgb10_configs overridden by environment. 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 [67607:67607:0418/195243.119611:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. ATTENTION: default value of option allow_rgb10_configs overridden by environment. [67607:67647:0418/195243.126235:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126351:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126456:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126504:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126555:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126602:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126660:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126719:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126782:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126842:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126898:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.126967:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127018:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127074:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127128:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127183:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127270:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127341:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127412:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127460:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127521:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127581:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127636:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127696:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127759:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127818:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127871:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127932:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.127999:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.128066:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.128129:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67607:67647:0418/195243.128184:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2) [67577:67577:0418/195243.479026:ERROR:browser_switcher_service.cc(238)] XXX Init() tcmalloc: large alloc 1073741824 bytes == 0x90b0dfa000 @ 0x561b09b8443b 0x561b12741c9c 0x561b0d00ba31 0x561b0cf98ab5 0x561b0cf98ed9 0x561b0f07dc7b 0x561b0f07c096 0x561b0eb27da5 0x561b0eb2c826 0x561b10ec3737 0x561b10ec348d 0x561b0cfa39ee 0x561b0cfb58e9 0x561b0cfb5e87 0x561b0cf6a27c 0x561b0cfb6119 0x561b0cf8c31a 0x561b0ce49b57 0x561b0acb5239 0x561b0acb6f45 0x561b0acb1b29 0x561b0ca59df5 0x561b0ca59ec4 0x561b0ca5a2df 0x561b0ca8f419 0x561b0ca57c96 0x561b09b51e05 0x7f738a6a71a3 [67577:67577:0418/195246.096136:FATAL:memory_linux.cc(37)] Out of memory. #0 0x561b0cff0809 base::debug::CollectStackTrace() #1 0x561b0cf53b26 base::debug::StackTrace::StackTrace() #2 0x561b0cf6481c logging::LogMessage::~LogMessage() #3 0x561b0d006ed0 base::(anonymous namespace)::OnNoMemorySize() #4 0x561b0d00ba45 operator new() #5 0x561b0cf98ab5 std::vector<>::_M_realloc_insert<>() #6 0x561b0cf98ed9 base::SplitStringUsingSubstr() #7 0x561b0f07dc7b extensions::autofill_util::GenerateAddressList() #8 0x561b0f07c096 extensions::AutofillPrivateEventRouter::OnPersonalDataChanged() #9 0x561b0eb27da5 autofill::PersonalDataManager::NotifyPersonalDataObserver() #10 0x561b0eb2c826 autofill::PersonalDataManager::OnWebDataServiceRequestDone() #11 0x561b10ec3737 WebDataRequestManager::RequestCompletedOnThread() #12 0x561b10ec348d base::internal::Invoker<>::RunOnce() #13 0x561b0cfa39ee base::TaskAnnotator::RunTask() #14 0x561b0cfb58e9 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl() #15 0x561b0cfb5e87 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() #16 0x561b0cf6a27c base::MessagePumpGlib::Run() #17 0x561b0cfb6119 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run() #18 0x561b0cf8c31a base::RunLoop::Run() #19 0x561b0ce49b57 ChromeBrowserMainParts::MainMessageLoopRun() #20 0x561b0acb5239 content::BrowserMainLoop::RunMainMessageLoopParts() #21 0x561b0acb6f45 content::BrowserMainRunnerImpl::Run() #22 0x561b0acb1b29 content::BrowserMain() #23 0x561b0ca59df5 content::RunBrowserProcessMain() #24 0x561b0ca59ec4 content::ContentMainRunnerImpl::RunServiceManager() #25 0x561b0ca5a2df content::ContentMainRunnerImpl::Run() #26 0x561b0ca8f419 service_manager::Main() #27 0x561b0ca57c96 content::ContentMain() #28 0x561b09b51e05 ChromeMain #29 0x7f738a6a71a3 __libc_start_main #30 0x561b09b51c5e _start Task trace: #0 0x561b10ec383d WebDataRequestManager::RequestCompleted() #1 0x561b0eb42d86 autofill::AutofillWebDataService::GetPaymentsCustomerData() Received signal 6 #0 0x561b0cff0809 base::debug::CollectStackTrace() #1 0x561b0cf53b26 base::debug::StackTrace::StackTrace() #2 0x561b0cfefe3a base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x561b0cff042e base::debug::(anonymous namespace)::StackDumpSignalHandler() #4 0x7f738c4fcb20 (/usr/lib64/libpthread-2.30.so+0x14b1f) #5 0x7f738a6bc625 __GI_raise #6 0x7f738a6a58d9 __GI_abort #7 0x561b0cfefa05 base::debug::BreakDebugger() #8 0x561b0cf64cb5 logging::LogMessage::~LogMessage() #9 0x561b0d006ed0 base::(anonymous namespace)::OnNoMemorySize() #10 0x561b0d00ba45 operator new() #11 0x561b0cf98ab5 std::vector<>::_M_realloc_insert<>() #12 0x561b0cf98ed9 base::SplitStringUsingSubstr() #13 0x561b0f07dc7b extensions::autofill_util::GenerateAddressList() #14 0x561b0f07c096 extensions::AutofillPrivateEventRouter::OnPersonalDataChanged() #15 0x561b0eb27da5 autofill::PersonalDataManager::NotifyPersonalDataObserver() #16 0x561b0eb2c826 autofill::PersonalDataManager::OnWebDataServiceRequestDone() #17 0x561b10ec3737 WebDataRequestManager::RequestCompletedOnThread() #18 0x561b10ec348d base::internal::Invoker<>::RunOnce() #19 0x561b0cfa39ee base::TaskAnnotator::RunTask() #20 0x561b0cfb58e9 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl() #21 0x561b0cfb5e87 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() #22 0x561b0cf6a27c base::MessagePumpGlib::Run() #23 0x561b0cfb6119 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run() #24 0x561b0cf8c31a base::RunLoop::Run() #25 0x561b0ce49b57 ChromeBrowserMainParts::MainMessageLoopRun() #26 0x561b0acb5239 content::BrowserMainLoop::RunMainMessageLoopParts() #27 0x561b0acb6f45 content::BrowserMainRunnerImpl::Run() #28 0x561b0acb1b29 content::BrowserMain() #29 0x561b0ca59df5 content::RunBrowserProcessMain() #30 0x561b0ca59ec4 content::ContentMainRunnerImpl::RunServiceManager() #31 0x561b0ca5a2df content::ContentMainRunnerImpl::Run() #32 0x561b0ca8f419 service_manager::Main() #33 0x561b0ca57c96 content::ContentMain() #34 0x561b09b51e05 ChromeMain #35 0x7f738a6a71a3 __libc_start_main #36 0x561b09b51c5e _start r8: 0000000000000000 r9: 00007fffe428fdf0 r10: 0000000000000008 r11: 0000000000000246 r12: 00007fffe4291060 r13: 00007fffe4291220 r14: 0000000000000049 r15: 00007fffe4291050 di: 0000000000000002 si: 00007fffe428fdf0 bp: 00007fffe4290040 bx: 00007f738c1b5240 dx: 0000000000000000 ax: 0000000000000000 cx: 00007f738a6bc625 sp: 00007fffe428fdf0 ip: 00007f738a6bc625 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated. '''
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.