Latest update breaks desktop and applications

#1
~]$ firefox
XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
libicui18n.so.63: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
~]$ docky
[Info  12:09:10.107] Docky version: 2.2.1.1 Release
[Info  12:09:10.111] Kernel version: 4.19.0.3
[Info  12:09:10.111] CLR version: 4.0.30319.42000
[Info  12:09:10.377] [ThemeService] Setting theme: Transparent
[Warn  12:09:10.412] [DesktopItemService] Could not find remap file '/home/asatysco2/.local/share/docky/remaps.ini'!
[Warn  12:09:10.710] [DrawingService] Error loading themed icon 'docky': Impossible de charger le module de chargement d’images : /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so : libicuuc.so.63: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type

And this :

l’installation de icu (63.1-2) casse la dépendance « icu<63.0 » requise par manjaro-settings-manager

Any turnaround ?

0 Likes

#2

To wait… there are other thread.

1 Like

#3

Surprise ! Cannot even revert to stable.
Which other threads ?

0 Likes

#4


0 Likes

#5

Ok, thank U !
Looks like someone published unverified packages… :thinking:
I could ultimately revert with :
sudo pacman -Syyuu

0 Likes

#6

It is called unstable for a reason.

Download and install qt5-base from this link

https://www.archlinux.org/packages/extra/x86_64/qt5-base/download/

then modify your pacman.conf and add qt5-base to the IgnorePkg=` list

3 Likes

#7

Thank U for info.
At this stage, I’ll rather wait a bit on stable.
Too many tweaks to be on track ! :stuck_out_tongue_winking_eye:

0 Likes

#8

Absolutely does what it says in the post title.
Before update everything works, after update:
firefox - broken
libreoffice - broken
pamac -broken
evolution -broken
icu - wont install

That is just what I happened to notice before I reverted to yesterdays snapshot in which everything works again.

No time to sort it our right now, but let it be a warning to others - don’t touch this update right now, wait for it to be fixed.

BTW ‘broken’ = won’t start.

0 Likes

#9

I’ll be cruel on this one, as it’s the first time in two years I see such a mess :
this is not “unstable” level, this is Ubuntu “proposed” level… :astonished:

0 Likes

#10

it’s unstable branch… things like that can happen as all “manjaro specific package” are built on this branche, and today, qt5-base (patched version from manjaro) needed to be rebuilt because of the new ICU… then all is normal… if you don’t want this kind of short time breakage… stay on testing or stable…

arch package arrive in this branche without rebuilt of manjaro own package/test before… as it’s on this branch all happen… then short time application breakage or even system (don’t start correctly) can happen.

as the time I’m writting it… philm rebuilt qt5-base and all is normal again.

1 Like

#11

When you think you’ve seen it all, you see people complaining of breakage in something called “unstable”.

And people wanted to put a switch in pamac in order to change branches easily! Maybe then they should change name from “unstable” to “hell’s gonna break loose”, in order to avoid confusions.

2 Likes

#12

But still issue is with manjaro-settings-manager wanting icu<63.0, right?

EDIT: my bad, see that deps have been updated to icu<63.2 :stuck_out_tongue:

0 Likes

#13

Yes, it’s corrected !
I’m back on unstable
My other computers are on Xubuntu devel & Debian testing for about 8 years, it’s my way of contributing as I report anytime I can.
This particular error was a bad surprise : unlike most bugs where a byzantine dependancy can accidentally break, this one was a replica of incidents that already happened in 2017/2016/2015…
That’s why I mentioned the Ubuntu proposed repository where devs dump anything, very often without any prior test or debugging. :wink:

0 Likes

#15

2 Likes

closed #16

This topic was automatically closed after 90 days. New replies are no longer allowed.

0 Likes