Arch Linux

Please read this before reporting a bug:

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!

FS#38326 - [libotr] Kopete OTR plugin doesn't work anymore

Attached to Project: Arch Linux
Opened by simunic (simunic) - Tuesday, 31 December 2013, 02:18 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 13 January 2014, 23:50 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andrea Scarpino (BaSh)
Sven-Hendrik Haase (Svenstaro)
Gaetan Bisson (vesath)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


The OTR plugin doesn't seem to work after update Kopete to 4.12.0-1. When I try to send a message in a OTR session, Kopete crash.

Additional info:
Kopete version: 4.12.0-1
With the update I'm using libotr instead of libotr3 (which worked fine before).

Steps to reproduce:
Open Kopete
Begin a conversation using an OTR session
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 13 January 2014, 23:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  libotr 4.0.0-5
Comment by Oracle Speaks (test0987654321) - Tuesday, 31 December 2013, 07:53 GMT
I can confirm that this is happening to me as well with the Kopete 4.12.0-1 update. I turned off the OTR plugin and now Kopete works again but with no encryption so that is no fix. When I turn OTR back on Kopete crashes the moment I send a message to someone. This must have something to do with Kopete 4.11.4-1 using OTR 3 and Kopete 4.12.0-1 using OTR 4. I am using the x86_64 Kopete 4.12.0-1 package.
Comment by Aurelieng (aurelieng) - Tuesday, 31 December 2013, 08:12 GMT
Very same setup and symptoms here too, just to mention that you guys are not the only one suffering from this bug.
Comment by Andrea Scarpino (BaSh) - Tuesday, 31 December 2013, 08:14 GMT
Comment by Craig (Hazey) - Thursday, 02 January 2014, 01:00 GMT
Fix not being applied upstream until January 9th (4.12.1), patch details at: or the actual patch file at

I would assume this will not be pulled downstream until 4.12.1 (around the 9th) when it's released upstream? Or will you be releasing a pkgrel ie 4.12.0-2 with the fix for kopete only? Just curious as (see below) I compiled the fix as 4.12.0-2 so just going to keep an eye out if you guys release it to just reinstall lol. Can also provide any further info if needed.

I applied the patch to the source manually and makepkg'd kopete then pacman -U and works fantastic, made a post about it via
Comment by Andrea Scarpino (BaSh) - Thursday, 02 January 2014, 07:42 GMT
This will be fixed in 4.12.1-1 package if either they apply it to git before or after the tagging. The key point is they apply them to git; then we can apply it to our PKGBUILD.
Comment by Andrea Scarpino (BaSh) - Monday, 06 January 2014, 11:10 GMT
please apply this upstream patch to libotr to fix Kopete segfault.
Comment by Gaetan Bisson (vesath) - Monday, 06 January 2014, 11:32 GMT
Sure. I've pushed libotr-4.0.0-3 to [testing]; feel free to close this report when you confirm that kopete is alright.
Comment by Oracle Speaks (test0987654321) - Monday, 13 January 2014, 23:45 GMT
I now have Kopete 4.12.0-1 and libotr 4.0.0-5 from Extra installed and have OTR turned on. I can confirm they are working perfectly. No more crashing. This bug is fixed for me. You can close this bug report as far as I'm concerned. Thank You!