Closed Bug 1060853 Opened 10 years ago Closed 8 years ago

bookmark can't be loaded (by manual way) or even after clean start

Categories

(SeaMonkey :: Bookmarks & History, defect)

SeaMonkey 2.29 Branch
x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1061672

People

(Reporter: haertetest_extrem, Unassigned)

Details

(Keywords: steps-wanted)

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1 (Beta/Release)
Build ID: 20140612174402

Steps to reproduce:

Started Beta 2 (Candidates; build 1) with a clean profile. Just the "old" bookmarks folder.


Actual results:

SM 2.29 beta 2 doesn't still load the bookmarks. also not by the manual way... causes "Backup can't be loaded"


Expected results:

SM 2.2.6.1 still loads the latest bookmark.entry, also by manual way. 

SM 2.29 beta 2 ( and still beta 1) doesn't do this simple thing.
Summary: bookmark → bookmark can't be loaded (by manual way) or even after clean start
Flags: needinfo?(nobody)
Ah, so what you're saying is this:

Bug 1061672 - Import json-file from Firefox do not work

How about we DUP to that (which then might end up being DUP'd to Bug 942937)
I don't use Firefox, only Seamonkey. I tried to load the Backup of the last bookmark (SM 2.26.1), but only with this problem.
Flags: needinfo?(nobody)
Version: SeaMonkey 2.29 Branch → SeaMonkey 2.31 Branch
Version changed due to https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines#version

Currently all indications I see underpin  therube's suspect "Bug 1061672"

@Reporter: Thank you for your attention. 
Please feel free to reopen this Bug if you find out that the fix for the other bug does not solve your problem or if you see other well founded indication that you fond an independent bug.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Keywords: steps-wanted
Resolution: --- → DUPLICATE
Version: SeaMonkey 2.31 Branch → SeaMonkey 2.29 Branch
You need to log in before you can comment on or make changes to this bug.