Closed
Bug 593058
Opened 14 years ago
Closed 14 years ago
Investigate how bug 533038 affects calendar code (timezone service file uris, binary components)
Categories
(Calendar :: Internal Components, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
1.0b4
People
(Reporter: Fallen, Assigned: ssitter)
References
Details
Attachments
(1 file)
593 bytes,
patch
|
Fallen
:
review+
|
Details | Diff | Splinter Review |
It seems in bug 533038 extensions will no longer be unpacked into the profile. This means we need to check how this will affect calendar, see if we can find a way to keep it backed, or ad <em:unpack>.
Reporter | ||
Comment 1•14 years ago
|
||
backed=packed
Comment 2•14 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100921 Firefox/4.0b7pre SeaMonkey/2.1b1pre - Build ID: 20100921124527
Warning: with <em:unpack>true</em:unpack> I get a crash at startup, see bug 597908 comment #4 and #6.
Assignee | ||
Comment 3•14 years ago
|
||
The 20100922 builds of Shredder and Lightning start without crash for me if <em:unpack>true</em:unpack> is added. Lightning doesn't work afterwards but that is already reported in Bug 591744.
Attachment #477875 -
Flags: review?(philipp)
Reporter | ||
Comment 4•14 years ago
|
||
Comment on attachment 477875 [details] [diff] [review]
force xpi unpacking
Since we have binary components, from what I heard this is needed anyway. We should definitely investigate those crashes/errors!
Attachment #477875 -
Flags: review?(philipp) → review+
Assignee | ||
Comment 5•14 years ago
|
||
Comment on attachment 477875 [details] [diff] [review]
force xpi unpacking
Pushed to <https://hg.mozilla.org/comm-central/rev/06bb6b6b1c2a>
Reporter | ||
Comment 6•14 years ago
|
||
Since we now force unpacking, the timezone service uris are the same and binary components can be read. Marking this bug as FIXED.
Assignee: nobody → ssitter
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0b3
Reporter | ||
Updated•14 years ago
|
Target Milestone: 1.0b3 → Trunk
You need to log in
before you can comment on or make changes to this bug.
Description
•