XaraLX does not start

Thanks for taking your time to report this issue and help making Ubuntu better.

I get the same error message when attempting to start xaralx. Ubuntu Trusty is also affected.

Additional info from another user:

Recenetly upgraded our web team to 13.10 from a mix of 12.04/13.04 on the desktop and am experiencing the same issues on both clean installs and upgrades. I see the same issue with both x64 and x32 versions and x32 app/libs running on an x64 base.

Interestingly, I download the ubuntu source package for 13.10 (0.7r1785-5ubuntu2), compiled and installed and it runs fine. Not sure why this is, i would have expected the source package to fail in the same way as the binary.

For now ive left it like this but would really like to be able to use ubuntu packages so that our users can do thier own updates.

Hi,

I also get the same issue in Trusty, with the kernel 3.13.0-24-generic #46-Ubuntu SMP x86_64

$ xaralx
xaralx: relocation error: xaralx: symbol _ZTV19wxGnomePrintFactory, version WXU_2.8 not defined in file libwx_gtk2u_core-2.8.so.0 with link time reference
$

Can confirm that I'm also getting this exact same error on 14.04. This was also present in Ubuntu 13.10 when I tried to run Xara then too.

Also on amd64

Update after migration to 14.04 x32:

I have updated our team to 14.04 now, I still have the same libwxgtk2-2.8 error as per Melodie and my 13.10 report.

My workaround (under 14.04) for the time being is to generate new working deb packages with apt-build from stock ubuntu source packages. You can do this quickly, easily and automagically with the following commands if you need a quick fix untill the ubuntu packages are fixed (holds breath):

sudo apt-get install apt-build
sudo apt-build install xaralx
sudo apt-get install xaralx-examples
winrar

If you want to save the packages for re-use on another system, the debs are saved in: "/var/cache/apt-build/repository/"
You will need the libxar-dev_0.7r1785-5ubuntu2+aptbuild1_i386.deb from there too.

If anyone needs i can throw the packages at a PPA for use.

This bug was fixed in the package xaralx - 0.7r1785-5ubuntu2build1

---------------
xaralx (0.7r1785-5ubuntu2build1) utopic; urgency=medium

  * No-change rebuild. Program no longer crash with relocation error on
    startup. (Fixes LP: #1247219)
 -- Hans Joachim Desserud <email address hidden> Wed, 09 Jul 2014 21:54:51 +0200

Hello Marcin, or anyone else affected,

Accepted into trusty-proposed. The package will build now and be available in a few hours in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

xaralx 0.7r1785-5ubuntu2build0.1 from trusty-proposed worked for me.

This bug was fixed in the package xaralx - 0.7r1785-5ubuntu2build0.1

---------------
xaralx (0.7r1785-5ubuntu2build0.1) trusty-proposed; urgency=medium

  * No-change rebuild. Program no longer crash with relocation error on
    startup. (Fixes LP: #1247219)
 -- Hans Joachim Desserud <email address hidden> Wed, 09 Jul 2014 21:54:51 +0200

The verification of the Stable Release Update for xaralx has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.