Closed Bug 956509 Opened 10 years ago Closed 6 years ago

Problem with omni.ja in instantbird-1.5 compiled against xulrunner-25.0

Categories

(Instantbird Graveyard :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: connor.behan, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20140103201958

Steps to reproduce:

There are two places in the build directory from which you should be able to run instantbird: mozilla/dist/bin and mozilla/dist/instantbird. One difference is that most files in "bin" are symlinks that point elsewhere in the build directory. But this can be changed with "cp -RL". Then the only remaining difference is that "instantbird" has most of its contents compressed into an omni.ja file.


Actual results:

Running from "bin" works but running from "instantbird" fails with:

WORKER ERROR DURING SETUP NS_ERROR_FAILURE: Failure
WORKER ERROR DETAIL undefined

Occasionally "Failure" is replaced by "Components not initialized". The only part of the GUI I can show is the profile manager with "instantbird -P". Compiling with --enable-debug doesn't work for some reason... gdb still tells me that instantbird-bin has no symbols.


Expected results:

The three directories that get packed into omni.ja are chrome, components and modules. If I start to recreate omni.ja in the "bin" directory, I can still get instantbird to start if I only put chrome in there. However, components and modules are more complicated because of the "jsloader/resource/app" stuff. Js files are precompiled by xpcshell from xulrunner so it is entirely possible that this is a xulrunner bug. However, firefox does the same thing and works fine when I build it against xulrunner.
On the behalf of Florian:
Closing bugs related to the Instantbird UI as WONTFIX, as the development of the standalone chat client Instantbird has stopped. Instantbird users are encouraged to migrate to Thunderbird. The user interface of instant messaging in Thunderbird will feel familiar, as the Thunderbird IM support started as a fork of Instantbird.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
On the behalf of Florian:
Closing bugs related to the Instantbird UI as WONTFIX, as the development of the standalone chat client Instantbird has stopped. Instantbird users are encouraged to migrate to Thunderbird. The user interface of instant messaging in Thunderbird will feel familiar, as the Thunderbird IM support started as a fork of Instantbird.
You need to log in before you can comment on or make changes to this bug.