Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Installation fails on 64bit Linux with

I downloaded the 1.2.1 tarball for installation on my SuSE 11.3 machine.

Install fails with the "symbol lookup error: /usr/lib64/libgdk-x11-2.0.so.0: undefined symbol: g_malloc_n" message.

I looked up a previous question on the same topic….


but that solution (removing the runtime files) doesn't work - the .titanium directory doesn't yet exist.

I see the license agreement window, press the continue button, and immediately it crashes with the libgdk message.

After the failed install, I see that the ~/.titanium directory now exists, but contains only one subdirectory, called appdata, so again, the removal of the "runtime" files can't be done.

— asked September 30th 2010 by Paul Hands
  • 11.3
  • 64bit
  • installation
  • libgdk-x11-2.0.so.0
  • linux
  • suse
1 Comment
  • I seem to be encountering the same issue here on my Fedora Core 13.
    How can I get more information to provide?

    — commented October 19th 2010 by Gustav Kampp

2 Answers

  • Looked harder on the solution provided in the link above, and discovered that files are installed in the /opt/titanium/ folder, because that was what I selected for my first installation attempt.

    So I followed the instructions and removed all lib files as mentioned in the solution:

    cd /opt/titanium/runtime/linux/1.0.0
    sudo rm libgobject-2.0.so
    sudo rm libglib-2.0.so

    sudo rm libgio-2.0.so
    sudo rm libgthread-2.0.so

    After this I could start the application - but only as root.

    — answered October 19th 2010 by Gustav Kampp
  • I don't suppose anyone has a better answer for this? I'm trying to install Titanium on my 64-bit Fedora 14 installation, and I'm seeing the exact same error.

    — answered February 4th 2011 by David Hicks
    1 Comment
    • David, please start a new question and explain your situation fully. Thanks

      — commented February 4th 2011 by Paul Dowsett
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.