#320 peazip qt i386 doesn't work in Kubuntu

[Eugene]

Kubuntu 14.04 LTS x32_64
Installes peazip_5.3.1.LINUX.Qt-2_i386.deb package. Trying to start peazip, we've got following console output:

$ peazip
peazip: symbol lookup error: peazip: undefined symbol: QApplication_hook_hook_commitDataRequest

[Dijx]

Same for me on Mint 13 on kubuntu 12.04 precise repos. (x64, Qt: 4.8.2, KDE: 4.13.0)

5.2.2 is last working version for me.

[Giorgio Tani]

Does the same occur with GTK2 version?
If the issue is limited to the Qt package, it is probably an issue of some GUI elements running on some versions of Qt libraries - already happened in the past, but I was able to detect the problem on my test machines.
In this case I can try to resolve the issue backtracking changes from 5.2.2 to 5.3 line in order to make the code not compiling for Qt target.

[Eugene]

GTK2 version are not installs because there are no libgmp3c2 package for Trusty, Saucy or Raring.

[Dijx]

Yep, I had to install libgmp3c2 and 3 more packages, but GTK2 was working, although i've uninstalled it - looks rather terrible on KDE ;]

[Eugene]

And also: #321 there is no QT x86_64 DEB package of peazip

[Dijx]

Unfortunately no change in peazip_5.4.0.LINUX.Qt-2_i386 :-(
Same behavior both on 12.04 and 14.04

[René Krell]

I can confirm this for OpenSUSE 13.1 / Tumbleweed:
peazip: symbol lookup error: peazip: undefined symbol: QApplication_hook_hook_commitDataRequest

[Rudi Pittman]

Doesn't appear to be a high priority given this is 4 years old and still occuring.
KDE Neon X86_64.

peazip: symbol lookup error: peazip: undefined symbol: QApplication_hook_hook_commitDataRequest

Make sure you upvote the issue by clicking on the + in first post.

[Giorgio Tani]

Support for Linux i386 has been dropped some versions ago.

[Rudi Pittman]

Great job replying to a ticket from 2014. I-386 was not abandoned back in 2014 when this a ticket was originally created. What a response time.

[Giorgio Tani]

The update was meant to clarify i386 Linux line is no longer under development, so the issue some users experienced with Qt4 on Linux i386 will not be analyzed further.

Lack of request in this time to resume the i386 development made me think that the correct thing to do at this point is closing the issue with WontFix status (which I don't really like to use) as the i386 development would not realistically re-start in future, and in any case not using the old Qt4 widget-set.