Closed
Bug 216431
Opened 21 years ago
Closed 19 years ago
canot add new bookmarks
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: cphil, Assigned: p_ch)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030815 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030815 Any new links added to the bookmarks are not saved when the browser is shut down. This occurs wheter the "Add Bookmark" is used, or whether they are added in the Bookmark Manager. Also, and new folders created in Bookmark Manager are lost when the browser is shut down. I only noticed this problem about one week ago. I'm not sure if it has occurred since I installed v1.5a, or has just recently started. Reproducible: Always Steps to Reproduce: 1.Add bookmark or new folder for bookmarks 2.Close the browser 3.restart the browser, and the new additions have vanished Actual Results: see above Expected Results: added the new linked bookmarks Classic theme... nothing else I can think of that would seem relevant
Comment 1•21 years ago
|
||
WFM on WinXP trunk 2003081515. Reporter: Did you install Mozilla on top of another installation ? If you did, please uninstall and delete your mozilla directory, and do a clean install. If it works, resolve this bug as WFM. Have you tried this using a fresh profile ? If not, please create a new profile, and try reproducing the problem. Is your Mozilla profile directory write-protected ?
Severity: major → normal
On further checking, I found that on Aug 5, 2003, at 7:05AM, which was well after the installation of the build of v1.5a, for some reason TEN THOUSAND zero byte bookmark-xxxx.html (where xxxx = a number from 1 to 9999) files were created in the following directory: \Documents and Settings\Administrator\ApplicationData\Mozilla\ Profiles\cphil\rm08r1ix.slt
Checked all files and directories and found none that were read-only.
It appears that I have worked around the problem by first closing the browser, renaming the bookmark.html files to bookmark.html.old, deleting the 9,999 other bookmark-xxxx.html files, restarting the browser to let it create a new bookmark.html file, then imported the old bookmarks to this new file. Only reason I didn't mark this as WFM now, it the unresolved issue as to the cause of the problem to start... Browser related, or caused by some external source. Ideas???
Comment 5•20 years ago
|
||
can you post bookmark.html.old as an attachment?
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 6•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 7•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•