FS#19768 - [skype] lib32-qt-4.6.3-1 breaks unicode input support in skype

Attached to Project: Community Packages
Opened by Paul Tsupikoff (GoodSoft) - Friday, 11 June 2010, 16:15 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 07 July 2010, 17:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Gavin Bisesi (Daenyth)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 7
Private No

Details

Description:

After upgrade to lib32-qt-4.6.3-1 inputting unicode characters in skype became impossible.
Copypasting still works.
When running skype the following is being output in console:

$ skype
QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv failed for BOM: Bad file descriptor
QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed
QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv failed for BOM: Bad file descriptor

Downgrading to lib32-qt-4.6.2-4 solves the problem.


Additional info:
* package version(s)
lib32-qt-4.6.3-1
bin32-skype-2.1.0.81-4


Steps to reproduce:

1. Upgrade to lib32-qt-4.6.3-1
2. Run skype
3. Try inputting non-ASCII characters from keyboard
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Wednesday, 07 July 2010, 17:03 GMT
Reason for closing:  Deferred
Additional comments about closing:  Not a problem with skype, but our lib32 in general.
Comment by Ionut Biru (wonder) - Friday, 11 June 2010, 16:59 GMT
i can't do anything about that. skype closed source. lib32-qt is qt i686. so check on a i686 system if qt 4.6.3+skype
Comment by Paul Tsupikoff (GoodSoft) - Friday, 11 June 2010, 17:58 GMT
Okay, seems that it works at i686.
Yet another x86_64-specific bug in skype :(
Comment by Michael Kogan (Photon) - Friday, 11 June 2010, 18:15 GMT
Would it help to report this upstream?

edit: I mean the QT/KDE people, not the Skype devs. :)
Comment by Victor (DELIRIUM) - Saturday, 12 June 2010, 04:49 GMT
Have sent a letter to skype support. Let's see what they will reply ;-)

I tried to send a report to QT upstream but http://bugreports.qt.nokia.com/ seems to be down.
Comment by Victor (DELIRIUM) - Tuesday, 15 June 2010, 09:48 GMT
Here is the reaction of skype support:

Thank you for contacting Skype Customer Service.

Thank you very much for the feedback.



We have forwarded this to the developers for further investigation.



In the mean time we wish to ask for your kind patience and understanding.
Should any further issues arise, please feel free to contact us again.
Comment by Pavel (heavyrail) - Saturday, 19 June 2010, 08:29 GMT
I can confirm this bug.
Temporary solution it to downgrade to lib32-openssl-0.9.8n and lib32-qt-4.6.2-4
Comment by Michael Kogan (Photon) - Saturday, 19 June 2010, 09:26 GMT
For me it's enough to downgrade to lib32-qt-4.6.2-4.
Comment by Pavel (heavyrail) - Saturday, 19 June 2010, 09:30 GMT
If I only downgrade lib32-qt, skype won't start reporting it couldn't find libssl.so.0.9.8
Comment by Michael Kogan (Photon) - Saturday, 19 June 2010, 10:45 GMT
Are you using lib32-openssl 1.0.0.a-2 and bin32-skype 2.1.0.81-4?
Comment by Ionut Biru (wonder) - Saturday, 19 June 2010, 10:46 GMT
i guess you have an out of date dependency.

just use LD_DEBUG=files skype > log 2>&1 and check the log of libssl and then pacman -Qo soname_that_Failes_to_load_libssl
Comment by Einar Lielmanis (spic) - Sunday, 20 June 2010, 16:53 GMT
If skype still crashes after downgrading lib32-qt, you may need to remove ~/.Skype/shared.xml.
Comment by Thomas Dziedzic (tomd123) - Sunday, 27 June 2010, 03:55 GMT
Please report this upstream.
Comment by Jan Alexander Steffens (heftig) - Wednesday, 07 July 2010, 05:29 GMT
This is actually a problem with lib32-glibc looking for gconv modules in /usr/lib/gconv. To fix this, start skype this way:

GCONV_PATH=/opt/lib32/usr/lib/gconv skype
Comment by Thomas Dziedzic (tomd123) - Wednesday, 07 July 2010, 05:34 GMT
Wouldn't this have to get fixed in bin32-skype?
Since I think that lib32-glibc installs to the proper location...
Comment by Jan Alexander Steffens (heftig) - Wednesday, 07 July 2010, 06:12 GMT
The solution would be to compile proper lib32 packages for the entire lib32 system instead of repackaging i686 packages. We would also need multilib support in our toolchain.

This is an arduous task noone wants to do. :P

Using GCONV_PATH isn't a real solution because while it fixes 32-bit programs, it will break any 64-bit programs they fork.
Comment by Gavin Bisesi (Daenyth) - Wednesday, 07 July 2010, 12:28 GMT
Is there any actual action that you want me to take on this?

Loading...