User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20080404 Firefox/220.127.116.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20080404 Firefox/22.214.171.124 This is message I sent to Foxmarks. They say error is due to serious bug in Firefox browser, but I could not locate similar bug report here. Difference in their report and my situation, is I'm not losing bookmarks, just getting the report that I am losing bookmarks. -------- Original Message -------- Subject: Disappearing_Bookmarks Date: Sat, 07 Jun 2008 11:39:17 -0400 From: Gary Schweinshaupt <email@example.com> Reply-To: firstname.lastname@example.org To: email@example.com Attached is error message received. (see message in your "Additional Information" below") My local bookmark set is not reduced and when I look on the Foxmarks server, the bookmark set is intact. Once I cancel the autosync process I can sync with no problem. This seems to has started after recent software updates. I've been using Foxmarks for more than a year, and this is the first problem I have encountered. It's getting very irritating having to deal with this every time I start my computer. Is there a way to go back to a previous version of Foxmarks or perhaps Firefox? I did some searching in help and FAQ areas, and couldn't find that others were having same problem. Thanks, Gary Schweinshaupt firstname.lastname@example.org --------------------------------- Reproducible: Always Steps to Reproduce: 1. start Foxfire first time of the day 2. get error message from "Foxmarks Settings" 3. I cancel out of autosync Here's link to screen capture of the error message I get. http://trowel.com/snapper-000044.png Here's link Foxmarks takes you to from the error message. http://wiki.foxmarks.com/wiki/Foxmarks:_Disappearing_Bookmarks
Bulk closing all UNCONFIRMED bugs dealing with places that haven't had any bug activity in over 120 days, have no votes, and are not enhancement requests. If you are still experiencing this issue in Firefox 3.0 or later, please re-open the bug with steps to reproduce (if they were not part of the original comment).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.