Hartmut Figge wrote:
> Dale:
>
>
>> If it still crashes after the upgrade today, I'm going to unmask
>> Seamonkey2 and see what it looks like.
>>
>
> One caveat. Your profile will be automatically migrated and you should
> be able to use SM2 or SM1. But for emails, if you fetch them with on
Hartmut Figge wrote:
> Dale:
>
>
>> start fresh and do whatever.
>>
>
> Nothing complicated, really. Start SM and create the old accounts
> exactly as they were before. Close SM and replace the folder Mail on the
> new profile with the folder Mail from the old profile.
>
That's basicall
Hartmut Figge wrote:
> Dale:
>
>> Hartmut Figge wrote:
>>
>
>
>>> No crash in the testprofile and you know, that something is wrong in the
>>> old one. And if the testprofile crashes you can go back to the old
>>> profile and have nothing lost but some minutes.
>>>
>> This is what
Hartmut Figge wrote:
> Dale:
>
>
>> A few days ago, I did rename .mozilla to .mozilla.old and it worked
>> fine. Then I copied over my emails, password files and bookmarks.
>>
>
> You should really test with a new profile as described. That is the
> standard way to test the integrity of a
Hartmut Figge wrote:
> Dale:
>
>
>> This appears to be a Seamonkey issue and I have no clue where to
>> start. I ran Seamonkey in a console as a user.
>>
>
> To recall. You have renamed ~/.mozilla, SM newly emerged so that it
> creates a new ~/.mozilla at the next start, not installed any
Hartmut Figge wrote:
>
> To recall. You have renamed ~/.mozilla, SM newly emerged so that it
> creates a new ~/.mozilla at the next start, not installed any extension
> and have now only the default plugin in about:plugins.
>
> And your SM crashes at http://wireless.att.com/
>
> Interesting. :)
>
Hartmut Figge wrote:
>
> Despite of the last one all should have disappeared after renaming
> /usr/lib/nsbrowser and restarting of SM. For me that worked. Hm.
>
> If your Shockwave Flash comes from the package adobe-flash, then
>
> h...@e675 ~ $ equery f adobe-flash
> [...]
> /usr/lib/nsbrowser/pl
Hartmut Figge wrote:
> Dale:
>
>
>> If it still crashes after the upgrade today, I'm going to unmask
>> Seamonkey2 and see what it looks like.
>>
>
> One caveat. Your profile will be automatically migrated and you should
> be able to use SM2 or SM1. But for emails, if you fetch them with on
Hartmut Figge wrote:
> Dale:
>
> [SM 1.x]
>
>> Archaic?
>>
>
> For me, yes. Since years i use nightlies of SM. Not quite correct,
> though, because i update the source, formerly from cvs, now with hg,
> apply my own patches and build my own SM.
>
>
>> I read about the new Seamonkey 2 but
Hartmut Figge wrote:
> Dale:
>
>
>> Well, I'm back again. I did a new profile by renaming .mozilla and then
>> copying over my emails, passwords and bookmarks. I didn't copy anything
>> else that I can recall. I also didn't copy prefs.js. I did edit it to
>> point to my old passwords file bu
Hartmut Figge wrote:
> Dale:
>
>
>> Well, I'm back again. I did a new profile by renaming .mozilla and then
>> copying over my emails, passwords and bookmarks. I didn't copy anything
>> else that I can recall. I also didn't copy prefs.js. I did edit it to
>> point to my old passwords file bu
Jon Hamilton wrote:
> On Wed, April 8, 2009 07:10, Dale wrote:
>
>> KH wrote:
>>
>>
>>> Dale schrieb:
>>>
>>>
>>>
Hi,
I have ran into a problem here. When I go to
http://wireless.att.com/
Seamonkey crashes. It does this pretty fast even tho I am on a s
Jon Hamilton wrote:
> On Wed, April 8, 2009 07:10, Dale wrote:
>
>> KH wrote:
>>
>>
>>> Dale schrieb:
>>>
>>>
>>>
Hi,
I have ran into a problem here. When I go to
http://wireless.att.com/
Seamonkey crashes. It does this pretty fast even tho I am on a s
Jon Hamilton wrote:
>
> I can't reproduce that either; the site loads/works fine for me. The site
> does use flash; perhaps it's a problem there? It might be worth turning
> on flashblock or otherwise disabling flash. Another suggestion would be
> to try it from a shell with a different home dir
14 matches
Mail list logo
