Closed
Bug 534710
Opened 15 years ago
Closed 15 years ago
Software Update misses libmozsqlite3.so - Restart fails - Program dead
Categories
(MailNews Core :: Build Config, defect)
MailNews Core
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 3.1a1
People
(Reporter: Hb, Assigned: standard8)
References
Details
(Keywords: fixed-seamonkey2.0.3)
Attachments
(1 file)
765 bytes,
patch
|
kairo
:
review+
kairo
:
approval-seamonkey2.0.3+
|
Details | Diff | Splinter Review |
Build: 2.1a1pre Seamonkey Nightly downloaded 20091207Z0905
1. The original download was extracted a week ago to the directory /home/<username>/seamonkey/ on Ubuntu 9.10. Program worked fine.
2. Clicking Help Menu item for "Software Update" or "Automated Update Service" or similar started a download.
3. At the Restart Now Or Later question Now was choosen.
4. Program does not start and console shows:
> /home/<username>/seamonkey/seamonkey-bin: error while loading shared
> libraries: libmozsqlite3.so: cannot open shared object file: No such
> file or directory load
Hint: Firefox 3.5.5 was running at update time for another user on the box.
Perhaps the commit/patch from dependent bug caused this.
Comment 1•15 years ago
|
||
When bug 513747 is resolved, our /suite/installer/unix/packages needs an update to the new file name.
Changing dependency from bug 519550 to 513747 and subject.
Summary: Software Update deletes libmozsqlite3.so - Restart fails - Program dead → Software Update misses libmozsqlite3.so - Restart fails - Program dead
Comment 3•15 years ago
|
||
http://hg.mozilla.org/comm-central/rev/07a296061f40 Mark Banner - Port Bug 513747 (rename sqlite3 library to mozsqlite3 to fix compile problems and crashes on Mac OS X) to comm-central + http://hg.mozilla.org/comm-central/rev/dfaf7c1acb84 Mark Banner - Bustage fix from porting of bug 513747 + http://hg.mozilla.org/comm-central/rev/afd382eea5b1 Serge Gautherie - Bug 534710 - Software Update misses libmozsqlite3.so - Restart fails - Program dead (Av1) Fix Unix packaging.
Assignee: nobody → bugzilla
Status: NEW → RESOLVED
Closed: 15 years ago
Component: General → Build Config
Flags: in-testsuite-
OS: Linux → All
Product: SeaMonkey → MailNews Core
QA Contact: general → build-config
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.1a1
Comment 4•15 years ago
|
||
Attachment #417694 -
Flags: review?(kairo)
Comment 5•15 years ago
|
||
Mark, it looks like Calendar may need the (same) update: http://mxr.mozilla.org/comm-central/search?string=sqlite3&case=on&find=%2Fcalendar%2Finstaller%2Fwindows%2Fpackages-static
Assignee | ||
Comment 6•15 years ago
|
||
(In reply to comment #5) > Mark, it looks like Calendar may need the (same) update: > http://mxr.mozilla.org/comm-central/search?string=sqlite3&case=on&find=%2Fcalendar%2Finstaller%2Fwindows%2Fpackages-static As Sunbird isn't planned to be supported past 1.0b1 (and it isn't built on trunk at the moment either), I'm not caring too much about what happens there, especially as I'm pretty sure their packages files are going to be out of date anyway.
Comment 7•15 years ago
|
||
Comment on attachment 417694 [details] [diff] [review] (Bv1-SM) Fix m-1.9.1 [Checkin: Comment 8] From what I see, this is needed on 1.9.1 only, to support downgrading, right? r/a=me for that.
Attachment #417694 -
Flags: review?(kairo)
Attachment #417694 -
Flags: review+
Attachment #417694 -
Flags: approval-seamonkey2.0.2+
Comment 8•15 years ago
|
||
Comment on attachment 417694 [details] [diff] [review] (Bv1-SM) Fix m-1.9.1 [Checkin: Comment 8] http://hg.mozilla.org/releases/comm-1.9.1/rev/3b599c1516e0
Attachment #417694 -
Attachment description: (Bv1-SM) Fix m-1.9.1 → (Bv1-SM) Fix m-1.9.1
[Checkin: Comment 8]
Comment 9•15 years ago
|
||
(In reply to comment #7) > From what I see, this is needed on 1.9.1 only, to support downgrading, right? Exactly.
Updated•15 years ago
|
Keywords: fixed-seamonkey2.0.2
Reporter | ||
Comment 10•15 years ago
|
||
The Software Update from 20091212 to today's version worked fine. The solution may be verified.
You need to log in
before you can comment on or make changes to this bug.
Description
•