Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#58440 - [loudmouth] [mcabber] breaks with libidn 1.34-2 in certain circumstances

Attached to Project: Community Packages
Opened by David J. Haines (dhaines) - Thursday, 03 May 2018, 13:56 GMT
Last edited by Jan de Groot (JGC) - Monday, 23 November 2020, 15:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 10
Private No

Details

Description:

Upon upgrade of libidn from 1.33-2 to 1.34-2, mcabber emits a "<JABBERID> is not a valid Jabber ID" error when attempting to send a message to a user in the roster. At least, this is the case with Cisco's UCUM Jabber implementation.


Steps to reproduce:

Upgrade libidn to 1.34-2.
Run mcabber
Attempt to send a message to a user in your roster.
Note error message in the logging window.
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 23 November 2020, 15:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  Assuming fixed, as mcabber and loudmouth have seen rebuilds in the meantime.
Comment by Kai Hildebrandt (derhil) - Friday, 04 May 2018, 17:11 GMT
Rebuild mcabber and loudmouth solved this issue for me.
Comment by Sergej Pupykin (sergej) - Monday, 07 May 2018, 11:32 GMT
loudmouth depends on libidn and it is in extra so I cannot rebuild it, reassigning this bug.
Comment by Johannes Wienke (languitar) - Saturday, 26 May 2018, 09:28 GMT
I was actually fine with just recompiling mcabber on multiple devices. I don't think recompiling loudmouth is strictly necessary.
Comment by Lukas Juhrich (lukasjuhrich) - Tuesday, 18 September 2018, 11:11 GMT
Same issue here. Not sure if helpful, but to expand, I observe the following error messages on startup:

```
mcabber: Symbol `stringprep_xmpp_nodeprep' has different size in shared object, consider re-linking
mcabber: Symbol `stringprep_xmpp_resourceprep' has different size in shared object, consider re-linking
mcabber: Symbol `stringprep_nameprep' has different size in shared object, consider re-linking
```
… followed by the normal mcabber startup log messages.

The login works, but the autojoin to jabber rooms fails because „<foo@conference.bar.baz> is not a valid Jabber room“.

Looking at readelf, the referenced functions come from libidn as mentioned, and ldd gives
```
libidn.so.11 => /usr/lib/libidn.so.11 (0x00007f76a487c000)
```
which is indeed owned by libidn 1.34-2.

Loading...