You are not logged in.

#1 2018-10-27 16:30:02

rogerthat
Member
Registered: 2018-08-14
Posts: 47

pacman libidn upgrade breaks rhythmbox

Yesterday, I ran pacman system update which included, among other things, libidn 1.34-2.0 -> 1.35-1.0 .
This immediately broke rhythmbox, which was unable to open:

rhythmbox: error while loading shared libraries: libidn.so.11: cannot open shared object file: No such file or directory

Offline

#2 2018-10-27 18:51:52

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: pacman libidn upgrade breaks rhythmbox

Have you tried building the aur package yet?

Offline

#3 2018-10-27 19:09:41

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: pacman libidn upgrade breaks rhythmbox

Hello again, Levi. smile

I'm afraid I don't follow you. In general, I just run "pacman -Syu" and things work.

Has rhythmbox been kicked out of the main repo's into AUR?

Offline

#4 2018-10-27 21:35:16

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: pacman libidn upgrade breaks rhythmbox

No, the package I linked is one based on its git repo, rather than a named released source tarball.  Those AUR packages exist in case someone wants something newer than the repo version, but in your case it might work around the versioning problem you have.  There's still a bug on the repo, but it might get you working while others work on a fix.  I myself have a few git-based projects cloned for a few things that have external dependencies that have a habit of breaking (I'm mainly looking at you, youtube), so that I can get a working version in the interim while a proper release is inbound.  In this case though, it's not an external dependency, it's a dependency on an old version of a library, but building your own version from the git source should work around that.

Once this issue does get resolved, you can get back on the official release channel by installing rhythmbox from the repos again.

Perhaps also rhythmbox should declare a versioned dependency on libidn (it doesn't, I checked).  That would allow this kind of dropout to be noticed before things hit the release channel.

Edit: libidn, not libicu.  That's the other defect raised in the past week here, d'oh!

Last edited by levi (2018-10-27 23:48:10)

Offline

#5 2018-10-27 21:46:00

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: pacman libidn upgrade breaks rhythmbox

Wow. Thank you for the explanation.

Offline

#6 2018-10-27 21:53:41

emgaron
Member
Registered: 2018-03-31
Posts: 2

Re: pacman libidn upgrade breaks rhythmbox

rhythmbox isn't the only package that is missing libidn.so.11 - lynx and elinks are also broken (same error). On my system, I have extracted libidn.so.11 from /var/cache/pacman/pkg/libidn-1.33-2-i686.pkg.tar.xz (i.e. the old version still in cache) and manually copied it to /usr/lib. Of course, this is only a stop-gap workaround and I will remove that file as soon as the other packages have been updated.

Offline

#7 2018-10-28 06:54:53

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 568
Website

Re: pacman libidn upgrade breaks rhythmbox

lynx is ok in testing (linked against libidn.so.12), but I cannot move it.
elinks and rhythmbox are not rebuild yet, so I priorized them.

Online

#8 2018-10-28 10:58:02

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 568
Website

Re: pacman libidn upgrade breaks rhythmbox

lynx and elinks are working in stable. rhythmbox doesn't build currently upstream.

Online

#9 2018-10-28 14:26:13

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: pacman libidn upgrade breaks rhythmbox

So should I monitor and wait until pacman shows an update is available?

Offline

#10 2018-10-28 15:21:53

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: pacman libidn upgrade breaks rhythmbox

andreas_baumann wrote:

lynx and elinks are working in stable. rhythmbox doesn't build currently upstream.

What does upstream mean in this context?  The testing or staging repos, or x64 or something else?

rogerthat: I suspect you might be in for a longish wait if you're waiting for a new build.  But if andreas can't build it it might also suggest you're likely to have trouble building the git aur on your machine, I guess.

Offline

#11 2018-10-28 18:04:16

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 568
Website

Re: pacman libidn upgrade breaks rhythmbox

upstream means original software breaks. so the -git version might have been fixed already.

Online

#12 2018-10-28 18:59:25

timsong
Member
Registered: 2018-04-03
Posts: 29

Re: pacman libidn upgrade breaks rhythmbox

vlc also will no longer run on my machine after recent system update, giving libidn error

[tim@oldlaptop ~]$ vlc
vlc: error while loading shared libraries: libidn.so.11: cannot open shared object file: No such file or directory

Offline

#13 2018-10-29 06:47:57

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 568
Website

Re: pacman libidn upgrade breaks rhythmbox

We should regress here and see what packages are using libidn. The list at https://packages.archlinux32.org/core/i686/libidn/
shows me that many of those packages are on the build-list. So I reckon the current problem is the speed the buildmaster
is handling and rebuilding packages.

Online

#14 2018-10-29 11:19:22

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 345

Re: pacman libidn upgrade breaks rhythmbox

abaumann: not only the speed of the buildmaster is lacking - some packages are blocked due to only-fixed-in-trunk-or-staging upstream packages (e.g. libxml2 blocks vlc)

Offline

#15 2018-10-29 11:24:35

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 568
Website

Re: pacman libidn upgrade breaks rhythmbox

Yeah. This is unfortunate. Then we have to patch downstream only to have it break later on when it's fixed upstream.

Online

#16 2018-10-29 12:15:35

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: pacman libidn upgrade breaks rhythmbox

Earlier, Levi said:
> Perhaps also rhythmbox should declare a versioned dependency on libidn (it doesn't, I checked).

Given the new discoveries, is that still considered a bug? And would I need to report that to archlinux upstream, or who?

Offline

#17 2018-10-29 12:18:16

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 345

Re: pacman libidn upgrade breaks rhythmbox

well, versioned dependencies is really optional candy - as far as upstream archlinux is involved.
And I'm afraid, we lack the manpower to add versioned dependencies to everything hmm

Offline

#18 2018-10-29 13:51:39

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 568
Website

Re: pacman libidn upgrade breaks rhythmbox

Online

#19 2018-11-08 03:28:40

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: pacman libidn upgrade breaks rhythmbox

I haven't seen any changes on the repos regarding rhythmbox or other libidn dependencies. Is there any news?
Is this problem already reported upstream in arch?

Offline

#20 2018-11-08 15:31:36

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: pacman libidn upgrade breaks rhythmbox

The link above is a report in upstream arch 64.  It includes hopeful instructions on how to build it, but it's a bit hacky, so unlikely to be built automatically like that, and especially not if it's not been tested on our configurations.  We're a little short of manpower to test it, and I personally have no interest in rhythmbox.

There's discussion above on rolling back libidn to version 11, and anything else using version 12 of it, but it seems that's not the only problem in the build dependencies.  It's going to take longer than a week and a bit to sort this out, I reckon.

Offline

#21 2018-11-08 15:51:42

rogerthat
Member
Registered: 2018-08-14
Posts: 47

Re: pacman libidn upgrade breaks rhythmbox

Thanks for the update. Running rhythmbox is nearly my entire use case for this old machine. hmm I'm having pacman ignore libidn for now. I'm just not sure how I will know it's safe to reenable?

Last edited by rogerthat (2018-11-08 15:52:07)

Offline

Board footer

Powered by FluxBB