Bug 1920379

Summary:	Crash with "Couldn't mmap icu data file"
Product:	[Fedora] Fedora	Reporter:	Pierguido Lambri <plambri>
Component:	qt5-qtwebengine	Assignee:	Kevin Kofler <kevin>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	fedoraproject.org, kde-sig, kevin, rdieter
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	qt5-qtwebengine-5.15.2-8.fc33	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-02 03:09:59 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 Pierguido Lambri 2021-01-26 08:28:19 UTC

Description of problem:
After updating to the latest qt5-qtwebengine, I get this error:

[0126/080606.005441:ERROR:icu_util.cc(251)] Couldn't mmap icu data file                                                                                                                                                                        

Version-Release number of selected component (if applicable):
qt5-qtwebengine-5.15.2-7.fc33.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Update qt5-qtwebengine to the latest version
2. Start qutebrowser (which depends on qt5-qtwebengine)


Actual results:
Qutebrowser cannot start

Expected results:
Qutebrowser should start normally

Additional info:

Downgrading to qt5-qtwebengine 5.15.2-1.fc33 fixes the issue.

Comment 1 Kevin Kofler 2021-01-26 12:06:23 UTC

Please:
1. Close all applications using QtWebEngine. If you are unsure, just restart your session (log out and back in) or reboot altogether. Rationale: QtWebEngine forks background processes from a "zygote" process. If the "zygote" process is old, it may still be built against the bundled ICU and look for the bundled data file, which is gone now that we switched back to the system ICU.
2. If you have qt5-qtwebengine-freeworld installed, upgrade it to qt5-qtwebengine-freeworld-5.15.2-2.fc33. Rationale: -2 is the corresponding version, built against the system ICU as well. -1 was built against the bundled ICU and wants the data file from the non-freeworld package.

Does that fix your issue?

Comment 2 Pierguido Lambri 2021-01-26 12:30:32 UTC

There are no other processes using QtWebEngine, just a bunch of terminals.
Removing the package qt5-qtwebengine-freeworld has fixed the issue. 
There was no update for it and having no other dependencies, I just removed it.
Thanks for the help.

Comment 3 Kevin Kofler 2021-01-26 12:47:16 UTC

https://koji.rpmfusion.org/koji/buildinfo?buildID=17750

I am going to add a versioned Conflicts to the Fedora update to force -freeworld to be upgraded as well.

Comment 4 Kevin Kofler 2021-01-26 12:56:49 UTC

Sorry, the above was the F32 build, this is the F33 one:
https://koji.rpmfusion.org/koji/buildinfo?buildID=17745

qt5-qtwebengine-5.15.2-8.fc33 with the versioned Conflicts building now.

In addition, I have also set the "suggest logout" flag on the update.

Comment 5 Fedora Update System 2021-01-26 18:46:25 UTC

FEDORA-2021-c91c2cae35 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c91c2cae35

Comment 6 Fedora Update System 2021-01-27 01:36:50 UTC

FEDORA-2021-c91c2cae35 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c91c2cae35`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c91c2cae35

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2021-02-02 03:09:59 UTC

FEDORA-2021-c91c2cae35 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.