profile issues with 2.56a

Discussion about Seamonkey builds
Posts: 9
Joined: May 16th, 2016, 1:08 am

Post Posted January 11th, 2018, 5:32 am

I tryed to launch seamonkey-2.56a1.en-US.win64 (2018-01-10-03-01-07-comm-central-trunk/) from temp dir. Alpha succefully get settings from profile, but lost bookmarks. When i returned to 2.49.1 bookmarks not appears. All attempts to restore bookmarks by bookmarks-manager was failed: "Unable to bla-bla.."
When I replace current places.sqlite from old backup, all bookmarks returned. Is it bug?


User avatar
Posts: 19533
Joined: December 7th, 2004, 8:51 pm
Location: Indiana

Post Posted January 11th, 2018, 6:44 am

I'm moving this to the Builds forum which is a better place for pre-release version discussion.
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.


User avatar
Posts: 18165
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted January 11th, 2018, 9:29 am

Are you using the same or different Profiles for the two versions of SeaMonkey?
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript


User avatar
Posts: 27168
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Post Posted January 11th, 2018, 3:33 pm

from viewtopic.php?f=6&t=3037076 "2.56a1 is currently only good as a virtual doorstopper."

Posts: 9
Joined: May 16th, 2016, 1:08 am

Post Posted January 12th, 2018, 6:46 am

therube, Same profile.
James, Yes, I know it. This is not help request. Just information. Maybe, I would like to know the reasons, but it is optional

Posts: 456
Joined: December 15th, 2015, 1:20 pm

Post Posted Yesterday, 6:17 am

The internal format of the bookmarks database places.sqlite changed between 2.49 and 2.56. You should not have lost the bookmarks during the upgrade but 2.56 is in a bad shape right now anyway which might have cuased it. We will retest it when it is in working order again (will probably take some time).

Going back was never supported so it might work or not. Usually indexed DB format also changes every second or third release and you have problems afterwards. So if you want to go back always use a backup unless you really know what changed and could fix it manually.


Return to SeaMonkey Builds

Who is online

Users browsing this forum: No registered users and 1 guest