Closed
Bug 108358
Opened 24 years ago
Closed 15 years ago
Bookmark File not locked
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
Future
People
(Reporter: 64bit, Unassigned)
References
Details
(Keywords: dataloss)
When I have reinstalled my system or having done something that the browser did
not like I often reinstall if it isn't humanly possible to restore. When I do so
I backup my profile bookmark-file and save it another place on the harddisk.
Afterwards I uninstall the browser and removes the profile directory. Then I
install the browser again. The browser starts and I see that I've forgotten to
put the bookmark-file to the directory. I close my browser-window and move the
file into the profile-directory and overwrite the bookmark-file. I have totally
forgotten to shut down the tray quick launch program and when I open a new
browser-window I see that my bookmarks have been deleted. I lost all of my
bookmarks - to bad. I would really like you to reopen the bookmark-file when
opening a new window or using the file as e.g. Word does, which means that you
simply cannot overwrite it while it is in use. That would be very nice. It has
happened to me several times, maybe because I don't think that much but it's
kind of anoying that it does like that.
Comment 1•24 years ago
|
||
confirming with win2k build 20011101..
The bookmark file isn't locked.
Mozilla should lock the bookmark (read-only)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: ReWriting bookmarks → Bookmark File not locked
Reporter | ||
Comment 2•24 years ago
|
||
That's correct.
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Updated•23 years ago
|
Blocks: profile-corrupt
Keywords: mozilla1.0.1
Comment 5•23 years ago
|
||
WFM 1.1 alpha trunk Build ID: 2002070204, Windows 98. I have Mozilla open. I try
to open bookmarks.html with WordPad. I can't open the file. The file must be locked.
Comment 6•23 years ago
|
||
Well, this is not working in Mozilla 1.3 series nightly build 2003021808. The
file is not locked as I can delete it. Critical severity, dataloss.
Severity: normal → critical
Updated•22 years ago
|
Blocks: bookmark-loss
Updated•22 years ago
|
No longer blocks: profile-corrupt
Comment 8•22 years ago
|
||
Mass reassign of my non-Firefox bugs to ben_seamonkey@hotmail.com
Assignee: bugs → ben_seamonkey
Status: ASSIGNED → NEW
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: ben_seamonkey → nobody
QA Contact: claudius → bookmarks
![]() |
||
Comment 9•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
![]() |
||
Comment 10•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
![]() |
||
Comment 11•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Group: core-security
![]() |
||
Comment 12•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
![]() |
||
Updated•16 years ago
|
Group: core-security
![]() |
||
Comment 13•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•