[3.4.0.24] libicui18n.so.63: cannot open shared object file

Bug Reports
,
1

REPRODUCIBILITY (% or how often): 100%
BUILD ID = OS VERSION (Settings > About product): 3.4.0.24
HARDWARE (Jolla1, Tablet, XA2,…): Xperia X
UI LANGUAGE: English
REGRESSION: (compared to previous public release: Yes, No, ?): Yes

DESCRIPTION:

Update from 3.4.0.16 -> 3.4.0.24

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. Update
  2. Boot
  3. jourtnalctrl (in recovery mode : I coudlnt boot till the end)

EXPECTED RESULT:

No errors like libicui18n.so.63: cannot open shared object file

ACTUAL RESULT:

Many errors from different packages complaining about
libicui18n.so.63: cannot open shared object file

Installed libicui18n.so.66

ADDITIONAL INFORMATION:

(see also journalctrl - 6 days more valid)

Is it safe to link libicui18n.so.66 to libicui18n.so.63?

1 Like
2

Which packages? Just inform the (openrepos I guess) developers to recompile for the new version. This might take some time if they use the standard SDK and not coderus’ docker container…

3

The packages listed to contain the error:

How about this question:

4

Is it safe to link libicui18n.so.66 to libicui18n.so.63?

Safe, yes. Correct, no.
No system app should use the so.63 library anymore, so your system and main apps will not have problems.
Some of the broken packages will stay broken, some might work. There is a reason the library version soname went from so.63 to so.66, it is not compatible.

5

Looking at the list of packages, there are system packages depending on old ICU. That means your upgrade didn’t finish correctly. You need to check the posts here with similar questions, there will be answers on how to fix a half-upgraded system.

6

Ive been trying to recover my system for days already … w/o success so far. Do you have a better idea?

7

Aha, all those topics from the 3.4 update are quite confusing to me, I cannot read them :slight_smile:

I did reply there:

1 Like