911827 - Bookmarks in sidebar reordered or revived (infrequently; using sync, formerly an ordering add-on)

Status: RESOLVED INCOMPLETE

(Firefox :: Sync, defect)

Description

[Max]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130803192641

Steps to reproduce:

Open bookmark sidebar.


Actual results:

Bookmarks appear in different order, or deleted bookmarks return out of order.


Expected results:

Bookmarks should be the same as last arranged.

Comment 1

[Max]

There are two issues I suspect may be related:

* I used an addon that alphabetized bookmarks. When it screwed up (not respecting folder boundaries) I removed it. That was many months ago.

* I use sync.

I see this happen only infrequently, but it just happened again so I thought I'd better report it.

Comment 2

[Liz Henry (:lizzard) (relman/hg->git project)]

Max, this support article might be helpful, https://support.mozilla.org/en-US/questions/776495 
It sounds like you might have a corrupt places.sqlite file, maybe from that plugin. Can you try backing up your bookmarks and restoring them?

Comment 3

[Max]

Thanks Liz! One clue that your diagnosis was correct is that I've been having problems closing ff cleanly; I've had to explicitly kill the old process ("sleeping") before I can start another.

I ran the "Places Maintenance" addon, closed ff, and could start ff again no problem. Maybe I'm cured.

Now I just have to find the motivation to manually reorder my enormous and much loved bookmarks library.

Comment 4

[Max]

I spoke too soon. I just had the unclean exit problem again (closed all windows, ff didn't terminate, had to kill).

Comment 5

[Mark Hammond [:markh] [:mhammond]]

Max, do you have any mobile devices attached to your Sync account?

Comment 6

[Julie McCracken (:julie)]

Thanks again for reporting this issue, but we are unable to determine the cause of the problem without the requested information. If you are able to provide this information, please just add a comment in this bug with that information and we'll get back to you as soon as we can, but in the meantime we are closing this bug so we can focus on the issues which we can address.