Closed
Bug 1097748
Opened 11 years ago
Closed 11 years ago
Thunderbird Daily failing to start, with "Couldn't load XPCOM." error
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Unassigned)
References
Details
(Keywords: regression)
STR:
1) Quit Thunderbird daily (running yesterday's build I believe)
2) Reopen it (presumably it updated on startup to today's build)
ER:
Opens fine
AR:
"Couldn't load XPCOM." error alert, which open pressing OK just results in the process exiting.
I don't know how best to find extra information to help with this. (eg I tried running via the console, but nothing was output to stdout/stderr)
application.ini says:
[App]
Vendor=
Name=Thunderbird
RemotingName=thunderbird
CodeName=Daily
Version=36.0a1
BuildID=20141112030203
SourceRepository=https://hg.mozilla.org/comm-central
SourceStamp=8247ad339166
ID={3550f703-e582-4d05-9a08-453d09bdfdc6}
Win8.1 x64, but win32 x86 build of daily.
| Reporter | ||
Comment 1•11 years ago
|
||
In case it wasn't clear, this occurs on every startup, and I can't find a way to successfully open Daily.
Comment 2•11 years ago
|
||
This is most likely due to bug 1084973, which has been backed out.
| Reporter | ||
Comment 3•11 years ago
|
||
Bad:
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2014-11-12-03-02-03-comm-central/
Good:
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2014-11-11-03-02-00-comm-central/
(In reply to Patrick Cloke [:clokep] from comment #2)
> This is most likely due to bug 1084973, which has been backed out.
Thanks :-)
| Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Patrick Cloke [:clokep] from comment #2)
> This is most likely due to bug 1084973, which has been backed out.
Indeed.
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Comment 5•9 years ago
|
||
I am getting same problem Error window comeup when click the Thunderbird icon.
Flags: needinfo?(textrade.machinery)
Updated•4 years ago
|
Flags: needinfo?(textrade.machinery)
You need to log in
before you can comment on or make changes to this bug.
Description
•