[SOLVED] Not sure where is the bug: libidn and lib32-libidn

Tharbad · 2018-09-15 16:28:48

Hi,

After the upgrade of lib32-libidn (v1.33-1 to v1.35-1) and libidn (v1.34-2 to v1.35-1) one of my steam games failed to run (both runtime and native). The error was "libidn.so.11 is missing". Downgrading both solved this problem. Is that a steam bug or libidn bug? Is it an Arch bug at all?

Thanks

Last edited by Tharbad (2018-09-18 13:28:48)

Trilby · 2018-09-15 16:46:36

Is it only one game that fails? Which one? What version of steam do you have installed?

Tharbad · 2018-09-15 16:48:29

The game is Dawn of war 2. steam is v1.0.0.56-1 and steam-native-runtime is 1.0.0.56-2.

brebs · 2018-09-15 19:03:45

You'll want a package which provides the old (version 11) libidn.so.11 - firstly, check whether you need a 32-bit or 64-bit version. Find the game executable, and run "file thegameexecutable", to see that.

Tharbad · 2018-09-15 20:29:17

64. I don't see such a package in AUR.

Tharbad · 2018-09-15 21:14:33

brebs wrote:

You'll want a package which provides the old (version 11) libidn.so.11 - firstly, check whether you need a 32-bit or 64-bit version. Find the game executable, and run "file thegameexecutable", to see that.

Lutris had the library. I copied it to a few locations related to steam. One of them did it. Thanks.

Do you that it's a good idea to create an AUR package for this?

philo · 2018-09-16 08:08:59

rainlendar-lite (AUR) gives the same error since libidn was upgraded, as reported on the AUR web page of that program.

Installing libn-git 1.33 (AUR) might solve the issue but it conflicts with libidn.

EDIT-
Copying from the libidn-1-34-2 package into /usr/lib/:

libidn.so.11
libidn.so.11.6.18

solved it for me.

Last edited by philo (2018-09-17 13:56:14)

brebs · 2018-09-16 08:42:05

Create a PKGBUILD which provides only libidn.so.11 - random example.

Lone_Wolf · 2018-09-16 12:58:27

$ pactree --sync steam-native-runtime | grep idn
│ │ ├─libidn2
│ │ │ ├─libidn
│ │ ├─lib32-libidn2
│ │ │ ├─libidn2
│   │   ├─libidn2
│ │ │ ├─lib32-libidn
│ │ │ │ └─libidn provides libidn>=1.35
$

OR figure out which dependency of steam-native-runtime needs a rebuild against latest libidn and file a bug report.

Last edited by Lone_Wolf (2018-09-16 12:59:05)

Tharbad · 2018-09-17 13:01:44

Lone_Wolf wrote:

$ pactree --sync steam-native-runtime | grep idn
│ │ ├─libidn2
│ │ │ ├─libidn
│ │ ├─lib32-libidn2
│ │ │ ├─libidn2
│   │   ├─libidn2
│ │ │ ├─lib32-libidn
│ │ │ │ └─libidn provides libidn>=1.35
$ 
OR figure out which dependency of steam-native-runtime needs a rebuild against latest libidn and file a bug report.

please elaborate. I have no idea what you just wrote.

triangle_soup · 2018-09-17 13:56:34

nm

Last edited by triangle_soup (2020-03-02 14:59:37)

brebs · 2018-09-17 16:07:14

triangle_soup wrote:

Can someone zip and ping me the 64bit version

You will already have it, in /var/cache/pacman/pkg/libinput-1.11.3-1-x86_64.pkg.tar.xz

Info at Downgrading page.

K3N8 · 2018-09-17 16:32:25

I had the same issue. Made a symlink named libidn.so.11 to the same source as libidn.so.12. That worked.

Scimmia · 2018-09-17 16:33:18

K3N8 wrote:

I had the same issue. Made a symlink ...

Don't do that. That's one of the stupidest things you can do to your system, and posting it here is completely irresponsible.

Last edited by Scimmia (2018-09-17 17:20:10)

brebs · 2018-09-17 16:52:49

I was just about to link to tons of compat examples, when I see: libidn-133-compat.

amaro · 2018-09-17 17:49:31

Have the same error for rainlendar.

Tried the link @brebs suggests

brebs wrote:

I see: libidn-133-compat.

and got

==> Validating source files with sha256sums...
    libidn-1.33.tar.gz ... Passed
    libidn-1.33.tar.gz.sig ... Skipped
    gcc7_buildfix.diff ... Passed
==> Verifying source file signatures with gpg...
    libidn-1.33.tar.gz ... FAILED (unknown public key 860B7FBB32F8119D)
==> ERROR: One or more PGP signatures could not be verified!
:: Unable to build libidn-133-compat - makepkg exited with code: 1

Downgrading libidn solved it for me

downgrade libidn
Available packages:

*  1) libidn-1.35-1-x86_64.pkg.tar.xz (remote)
*  2) libidn-1.35-1-x86_64.pkg.tar.xz (local)
*  3) libidn-1.34-2-x86_64.pkg.tar.xz (remote)
*  4) libidn-1.33-2-x86_64.pkg.tar.xz (remote)
   5) libidn-1.33-1-x86_64.pkg.tar.xz (remote)
   6) libidn-1.32-1-x86_64.pkg.tar.xz (remote)

select a package by number: 4
[sudo] password for vb: 
 libidn-1.33-2-x86_64            208.6 KiB  33.9K/s 00:06 [-------------------------------] 100%
 libidn-1.33-2-x86_64.sig        310.0   B  0.00B/s 00:00 [-------------------------------] 100%
loading packages...
warning: downgrading package libidn (1.35-1 => 1.33-2)

brebs · 2018-09-17 18:20:44

amaro wrote:

FAILED (unknown public key

So Google the error. Investigate and learn.

K3N8 · 2018-09-17 19:05:20

Scimmia wrote:

Don't do that. That's one of the stupidest things you can do to your system, and posting it here is completely irresponsible.

Good to know! I posted this because of a simular issue I had with google-musicmanager from AUR. It was posted as a solution there and it worked.

brebs · 2018-09-17 19:39:17

K3N8 wrote:

It was posted as a solution there and it worked.

I've added a FAQ entry against symlinking

K3N8 · 2018-09-17 19:46:52

@brebs I've removed the symlink and installed libidn-133-compat. Thank you!

amaro · 2018-09-18 05:13:40

brebs wrote:

So Google the error. Investigate and learn.

Thank you, brebs! That was really kind. Got it working.

triangle_soup · 2018-09-18 13:40:25

nm

Last edited by triangle_soup (2020-03-02 14:58:53)

Scimmia · 2018-09-18 13:46:57

Note that downgrading that package would break everything else that uses it. Very bad idea, and partial updates are not supported.

triangle_soup · 2018-09-18 14:51:39

nm

Last edited by triangle_soup (2020-03-02 14:59:14)

Scimmia · 2018-09-18 14:56:01

brebs gave you the correct solution all the way back in post #15

Arch Linux

#1 2018-09-15 16:28:48

[SOLVED] Not sure where is the bug: libidn and lib32-libidn

#2 2018-09-15 16:46:36

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#3 2018-09-15 16:48:29

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#4 2018-09-15 19:03:45

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#5 2018-09-15 20:29:17

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#6 2018-09-15 21:14:33

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#7 2018-09-16 08:08:59

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#8 2018-09-16 08:42:05

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#9 2018-09-16 12:58:27

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#10 2018-09-17 13:01:44

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#11 2018-09-17 13:56:34

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#12 2018-09-17 16:07:14

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#13 2018-09-17 16:32:25

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#14 2018-09-17 16:33:18

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#15 2018-09-17 16:52:49

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#16 2018-09-17 17:49:31

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#17 2018-09-17 18:20:44

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#18 2018-09-17 19:05:20

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#19 2018-09-17 19:39:17

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#20 2018-09-17 19:46:52

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#21 2018-09-18 05:13:40

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#22 2018-09-18 13:40:25

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#23 2018-09-18 13:46:57

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#24 2018-09-18 14:51:39

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

#25 2018-09-18 14:56:01

Re: [SOLVED] Not sure where is the bug: libidn and lib32-libidn

Board footer