{ "id": "61862", "key": "TIMOB-1230", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-15T02:47:15.000+0000", "created": "2011-04-15T02:47:13.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "desktop" ], "versions": [], "issuelinks": [], "assignee": { "name": "rseagraves", "key": "rseagraves", "displayName": "Reggie Seagraves", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-09T21:25:03.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
The gtk libraries shipped with the Titanium Desktop (1.0?)\nruntime installed by Titanium Developer conflict with system\nlibraries, GTK complains about exported symbols. The temporary fix\nis to delete libglib libgobject libgthread* and so on from\n~/.titanium installation. Hope for a renewed packaging so that\ndwployment is doable.
I've attached the bash script i'm using to perform a working\ninstallation of the runtime for test purposes.
Is there any chance of a fix for this? It's extremely painful\nfor end-users.
Really the situation on ubuntu lucid 10.04 is even worse.... As\nfrom this releaseP Python2.5 isn't even available as a package to\ninstall but the python module of titanium desktop depends on it and\nfail silently if it was required as a language in the app but isn't\navailable on end-user system. Very sad...
Not a mobile bug. File as a desktop bug.
Stephen, are you joking? i reported it as Desktop bug, look at\nthe title