Iceape update in Squeeze has erased (?) bookmarks

[AG]

Today I accepted the update in Squeeze for Iceape. However, this
appears to have erased my old/ previous bookmark and password files that
I used in Iceape before the upgrade. I have searched through all of the
relevant dot files and I can't see anything. Is this standard procedure
for a browser upgrade to erase files like bookmarks, etc.? Firefox and
Opera have never done this, so why would Iceape? Has Iceape renamed
them, backed them up somewhere perhaps?

Thus far there is nothing shown through Google on this issue, so
wondering if anyone else here has come across this and - more critically
- found a way around it?

Thanks for any assistance before I tear the remainder of my hair out!

AG

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[AG]

AG wrote:
> Today I accepted the update in Squeeze for Iceape. However, this
> appears to have erased my old/ previous bookmark and password files
> that I used in Iceape before the upgrade. I have searched through all
> of the relevant dot files and I can't see anything. Is this standard
> procedure for a browser upgrade to erase files like bookmarks, etc.?
> Firefox and Opera have never done this, so why would Iceape? Has
> Iceape renamed them, backed them up somewhere perhaps?
>
> Thus far there is nothing shown through Google on this issue, so
> wondering if anyone else here has come across this and - more
> critically - found a way around it?
>
> Thanks for any assistance before I tear the remainder of my hair out!
>
> AG
>

Sorry for the bad form of replying to my own post.

I have now located the bookmark.html file and cp'd that over to the
seamonkey directory.

Now I need to recover the passwords - does anyone know what those might
be called under Iceape?

Cheers

[Jochen Schulz]

AG:

>
> Today I accepted the update in Squeeze for Iceape. However, this
> appears to have erased my old/ previous bookmark and password files that
> I used in Iceape before the upgrade. I have searched through all of the
> relevant dot files and I can't see anything. Is this standard procedure
> for a browser upgrade to erase files like bookmarks, etc.?

No. Package upgrades *mustn't* overwrite or delete any user data.

However, it is entirely possible that Iceape has changed the location
where it stores and reads its configuration. Do you know the place where
your settings have been previously? It may be somewhere below ~/.mozilla
or directly in ~/.iceape.

A "brute-force" method would be to search for a known filename in your
home:

$ find ~ -name bookmarks.html

But I don't know whether Iceape still uses the file bookmarks.html or
some other file instead.

J.
--
Quite often I wonder why I am not more famous and/or more wealthy.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>

[Jochen Schulz]

AG:

>
> I have now located the bookmark.html file and cp'd that over to the
> seamonkey directory.

And it works?

> Now I need to recover the passwords - does anyone know what those might
> be called under Iceape?

Firefox/Iceweasel uses, IIRC, the files secmod.db and signons*. But that
is documented somewhere on mozilla.org, you should be able to find exact
instructions there.

J.
--
I cannot comprehend the idea of chemical and biological weapons.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>

[AG]

Jochen Schulz wrote:

AG:
  

I have now located the bookmark.html file and cp'd that over to the  
seamonkey directory.
    

And it works?
  

Apparently, yes.

Now I need to recover the passwords - does anyone know what those might  
be called under Iceape?
    

Firefox/Iceweasel uses, IIRC, the files secmod.db and signons*. But that
is documented somewhere on mozilla.org, you should be able to find exact
instructions there.
  

Cheers!  That confirms actions I took yesterday evening.  I was working on the premise that one of those files must store the hash-table, and I did see the secmod.db file (no signon) in the default of ~/.mozilla and secmod.db plus signons.sqlite in the ~/.mozilla/seamonkey directory.  I backed up the seamonkey secmod.db and cp the secmod.db from the default into seamonkey.  Fired up seamonkey and no go. 

To be honest, this is more of a PITA than the issue with the bookmarks was.  But that part is sorted, and I know what I'm looking for now should this kind of thing happen again, so ... I'm happy with that result.

Thanks for responding to my call for help, Jochen!

AG

J.