Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1352236 - seamonkey-2.40-3.fc24.x86_64 mailer crash
Summary: seamonkey-2.40-3.fc24.x86_64 mailer crash
Keywords:
Status: CLOSED DUPLICATE of bug 1350144
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-02 21:32 UTC by Yves L'ECUYER
Modified: 2016-07-03 13:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-03 13:51:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Yves L'ECUYER 2016-07-02 21:32:25 UTC 
Description of problem:
After Fedora 23 to Fedora 24 upgrade, I cannot use any more the mailer part of seamonkey. With my current account, as soon as I try to open the mailer, seamonkey crashes

If I remove my $HOME/.mozilla/seamonkey directory, I can open it, but at the end of creation of a new mail account, mozilla crashes again 

Other functionalities: web browser or composer seams to work normally

Version-Release number of selected component (if applicable):
seamonkey-2.40-3.fc24.x86_64


How reproducible:always


Steps to Reproduce:
1.
2.
3.

Actual results:seamonkey mailer unusable


Expected results:a mailer component working normally, as so many tenth years now


Additional info:
Comment 1 Dmitry Butskoy 2016-07-03 13:46:58 UTC 
*** Bug 1352243 has been marked as a duplicate of this bug. ***
Comment 2 Dmitry Butskoy 2016-07-03 13:51:57 UTC 

*** This bug has been marked as a duplicate of bug 1350144 ***
Note You need to log in before you can comment on or make changes to this bug.