Cruz, Jaime wrote:
Ed Mullen wrote:
Cruz, Jaime wrote on 12/19/2014 8:11 PM:
Eureka! I found it! There were FOUR files all prefixed by
"places.sqlite" including the original file. If I delete all four and
copy in the "places.sqlite" from my Windows system to my Linux system,
it works! I only have to copy that one file.
Again, this wasn't necessary until 2.29 came along, so I wonder what
changed??
Do not understand. I don't care how many files contain places.sqlite in
their filenames, copying the specific fiel "places.sqlite" should do the
trick.
Just to make things clear, I ALWAYS shut down Seamonkey BEFORE I copy
places.sqlite from the source system, and I ALWAYS shut down Seamonkey
on the target system BEFORE I move over the copy. It didn't matter. I
think the "SHM" and "WAL" files had to be in sync with the base file, or
it ended up creating a "CORRUPTED" file and I had no bookmarks at all.
Deleting ALL of the places.sqlite* files from the target directory
before copying in the new places.sqlite does the trick. When I restart
Seamonkey it has all of the bookmarks and history, and it recreates the
SHM and WAL files.
This was true for my copy of Firefox running under VirtualBox on my
machine as well. Had to do the same there, too. Never had to do this
before Seamonkey 2.29 so SOMETHING changed.
Why is it that SeaMonkey is unable to restore bookmark backups that it
makes itself? Why does it even fail to recognize the extension name of
the automatic backups?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
