By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1431 - Android Development Tools and Aptana Studio 3 crash on startup
Summary: Android Development Tools and Aptana Studio 3 crash on startup
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: qt3 (show other bugs)
Version: 3.5.13.1 [Trinity]
Hardware: amd64 Kubuntu Precise
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-04-06 13:13 CDT by John Willis
Modified: 2013-04-11 21:58 CDT (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Willis 2013-04-06 13:13:00 CDT 
When attempting to run Aptana Studio 3 or the Android Development Tools (both Eclipse-based) in TDE 3.5.13.1, I get the following:

Aptana Studio 3:

jollis@poseidon:~$ /opt/Aptana_Studio_3/AptanaStudio3
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gtk-qt-application path = <unknown> pid = 10827

ADT:

jollis@poseidon:~$ /opt/adt-bundle-linux-x86_64-20130219/eclipse/eclipse
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gtk-qt-application path = <unknown> pid = 10890


However, if I run with superuser privileges (sudo), they work. Also, if I remove the gtk-qt-engine-trinity and kgtk-qt3-trinity packages, both applications work. However, in this instance, the console output shows the following message over and over again:

ERROR: ld.so: object '/opt/trinity/lib/kgtk/libkgtk2.so' from LD_PRELOAD cannot be preloaded: ignored.

Running the apps under gdb yielded no further (useful) information.
Comment 1 Timothy Pearson 2013-04-06 14:37:19 CDT 
This is related to kgtk-qt3-trinity (which is now strongly deprecated and will be remoted in a future release).

Have you logged out and logged in after removing kgtk-qt3-trinity?
Comment 2 John Willis 2013-04-06 16:02:46 CDT 
(In reply to comment #1)
> This is related to kgtk-qt3-trinity (which is now strongly deprecated and will
> be remoted in a future release).
> 
> Have you logged out and logged in after removing kgtk-qt3-trinity?

Logging out and back in had no effect, but running ldconfig and _then_ logging out and back in took away the libkgtk2.so error.

In any event, Aptana and ADT are running flawlessly now, and several orders of magnitude faster than they did under KDE4. Awesome project!
Comment 3 Timothy Pearson 2013-04-06 17:01:28 CDT 
Interesting.  I suppose I should update the kgtk-qt3-trinity package to run ldconfig on both installation and deinstallation to avoid this problem in the future.
Comment 4 Timothy Pearson 2013-04-08 12:30:35 CDT 
(In reply to comment #3)
> Interesting.  I suppose I should update the kgtk-qt3-trinity package to run
> ldconfig on both installation and deinstallation to avoid this problem in the
> future.

This has been implemented in GIT hash 35be850.

Thanks for reporting!