On 07/21/2010 05:33 PM, Kelly Clowers wrote:

On Wed, Jul 21, 2010 at 15:00, Ron Johnson<ron.l.johnson@cox.net> wrote:

[snip]

Reusing an in-place .mozilla/firefox tree when migrating from i386 to amd64
proved subtly problematic, though, in many ways.


What kind of problems? I don't remember having problems... although maybe
that was the 2.x era, or maybe I just don't remember it.



Subtle things like plugins not working properly.

--
Seek truth from facts.


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

Archive: 4C478482.8090400@cox.net">http://lists.debian.org/4C478482.8090400@cox.net

On Wed, 21 Jul 2010 18:36:34 -0500, Ron Johnson wrote:

> On 07/21/2010 05:33 PM, Kelly Clowers wrote:
>> On Wed, Jul 21, 2010 at 15:00, Ron Johnson wrote:
> [snip]
>>> Reusing an in-place .mozilla/firefox tree when migrating from i386 to
>>> amd64 proved subtly problematic, though, in many ways.
>>
>> What kind of problems? I don't remember having problems... although
>> maybe that was the 2.x era, or maybe I just don't remember it.
>>
>>
> Subtle things like plugins not working properly.

On default installations, Iceweasel plugins are installed in a common
path (such "/usr/lib/iceweasel/plugins") and not on each user's profile,
so AFAIK, moving/copying a profile (~./mozilla) should not interfere with
this.

Problems can arise when transferring profiles between different browser
releases, though.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.07.22.06.48.40@gmail.com">http://lists.debian.org/pan.2010.07.22.06.48.40@gmail.com