Closed Bug 136507 Opened 23 years ago Closed 15 years ago

broken localstore.rdf causes Address Book to display empty

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: masri, Unassigned)

References

Details

Attachments

(1 file)

Platform: PowerBook G3/300/192Mb/48Gb, MacOS X 10.1.3 Fizzilla Build: 2002040908 In the latest builds of Fizzilla on MacOS X 10.1.3, an address book with lots of addresses appears empty when you go to Window: Address Book. This works fine in 0.9.9. - Adam
Platform: PowerBook G3/300/192Mb/48Gb, MacOS X 10.1.4 Fizzilla Build: 1.0RC1 (2002041712) After a bit of trial and error, I believe this bug is a new localstore.rdf bug. I found that trashing my localstore.rdf and relaunching Moz allowed my address book to display properly. Replacing with the broken localstore.rdf and relaunching Moz lead to my address book appearing empty once again. I've removed a lot of data from my "broken" localstore.rdf and attached it to this report. Hopefully this will give you enough to go on to fix this new bug. - Adam
Summary: Address book with addresses displays empty in latest builds → broken localstore.rdf causes Address Book to display empty
Please disregard any pr0n I didn't remove...
mass re-assign.
Assignee: racham → sspitzer
Product: Browser → Seamonkey
Assignee: sspitzer → mail
QA Contact: nbaca → addressbook
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: