Closed Bug 169537 Opened 23 years ago Closed 22 years ago

Can not compose mail messages

Categories

(MailNews Core :: Composition, defect)

Product:
MailNews Core
Component:
Composition
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: hershberger, Assigned: bugzilla)

References

Details

Unable to type in the text body section of the mail message composer window, all other windows and input points respond as expected. I am using v 1.1 for the Windows OS, my machine is a Win98 platform.
May be a dup of 167585, reporter can you review 167585 to see if the steps in that bug are similiar to what your steps would be.
*** Bug 169535 has been marked as a duplicate of this bug. ***
NO. This happens to me regardless of machine status when I open a "Compose New Message" window there is no response in the body text window, no cursor, no text typed. I have restarted the app, and have also rebooted with the same effect. The ultimate problem is the same in both this and bug #167585, but what I am seeing is an all the time problem (which might of course just be a problem with my system). Reproducibility is 100%. History: I installed version 1.2 on Sunday Morning, had problems (mail client crash on open) with it, so installed the Daily build for that day, had problems (mail client crash on open, no tabbed browsing) with that. So assuming I had a corrupt install file I d/l'd version 1.2 again, and reinstalled it. Had the same problem. So I stepped back to version 1.1 (tabbed browsing is back, no crash when opening mail client), but now am unable to compose messages. Things I have not done: Uninstalled and reinstalled Mozilla. Complete wipe and rebuild of OS. But I am getting tempted to do either or both of these things as this problem continues to manifest itself. (basically that is a thinly veiled plea to you developer types that such drastic measures are unnecessary...) Ok thanks for your time. R
Can you create a new profile, you don't have to delete the one that doesn't work, and add your mail account to see if we have an app problem or a profile problem. If your mail is POP, please check the box to leave msgs on server before you log into this account. I just want to see if the compose window works in the new profile, if so then we can trouble shoot why it's not working in your existing profile. Thanks.
If I create a new profile then another bug rears its ugly little head (loss of old profile mapping) and it takes about an hour to resolve back to where I was. I can create a new profile, but it won't happen till this weekend, when I have sometime to clear it up and get it back to what it was. Another thing I could try is installing on a different machine (that didn't initially have Mozilla), but that might add other variables into the mix. Let me know how you would like me to proceed. The new profile option won't happen for a couple of days, vis the new machine which would happen today (about 5pm my time, which is GMT-10, as I am in HI). Thanks for your time.
It would be helpful to try this on the same system with the same build new profile. Robert, regarding the ugly bug you would run into if you create a new profile: When you say the loss of Profile mapping are you talking about your mail accounts, preference settings and address book don't show up in the profile sometimes after relaunching? If so, that is bug 155080 (prefs.js file getting rewritten sometimes when exiting with Quick Launch=On for single profile users). We fixed the non commercial part of that bug on 8-8 but the commercial part fix has not been checked in yet. To protect yourself from this bug, make a copy of your prefs.js file (don't rely on the prefs.bak file in the .slt directory because that one gets updated with the corrupted one when the corruption happens). Now if the corruption happens and you lose your mapping to your mail accounts and preference settings, just exit the app and replace the prefs.js file (probably shows a size of 1kb) with the copied prefs.js file. So if thats the problem you are trying to avoid, make a copy of your prefs.js file, exit the app, disable the Quick Launch Icon from the task tray. Launch Profile Manager and create the new Profile. If you don't think 155080 is what you were running into as the ugly bug, then try it on another machine. Thanks for your help on this.
Ok on Saturday I opened Profile Manager and noted no Profiles listed. So I attempted to create a new profile, which went well at least on paper. I was able to click through all the buttons and get back to Manage Profiles or Start Mozilla Window, and the new Profile displayed (of course the old profile was not displayed). But when I clicked on the Start Mozilla button nothing happened. Figured something was messed up on the computer. Shut down Mozilla tried again, no joy. Rebooted, tried again, no joy. So I uninstalled Mozilla, and reinstalled it. rebooted started Mozilla, the Profile Window comes up to choose a profile, choose my original profile and now I can compose email. Restarted Mozilla choose a different profile, and could compose under that one too. Restarted Mozilla, deleted (using Profile Manager) all the profiles except my original one, and haven't see the mail problem since. But since the profile info had been all cocked up my proxy info was also incorrect, and it took me a while to figure that out (sometimes I'm not so bright). What I think might have happened is that I installed a nightly build (a week ago or more now) and that problem (no mail compose) showed up. So when I reinstalled an older version of Mozilla it didn't clear out the previous version -- I just paved over the old install. So it looks like the nightly build added a file the old installer didn't know about, and I live and learn. I appreciate your help with this, I now think the originial problem is in the nightly build, not v1.1 which is where I'm at right now. Maybe this weekend I will up date to the next nightly build, but maybe not... :) As to the profile loss problem I mentioned earlier, I didn't experience it fully or partially, some settings didn't transfer -- Proxy is the one that I remember, but I think I had to reset extentions (under advanced--systems tab) and the Tabbed Navigation settings, both where at their default levels. Thanks again. Have a good day. Robert
Ok on Saturday I opened Profile Manager and noted no Profiles listed. So I attempted to create a new profile, which went well at least on paper. I was able to click through all the buttons and get back to Manage Profiles or Start Mozilla Window, and the new Profile displayed (of course the old profile was not displayed). But when I clicked on the Start Mozilla button nothing happened. Figured something was messed up on the computer. Shut down Mozilla tried again, no joy. Rebooted, tried again, no joy. So I uninstalled Mozilla, and reinstalled it. rebooted started Mozilla, the Profile Window comes up to choose a profile, choose my original profile and now I can compose email. Restarted Mozilla choose a different profile, and could compose under that one too. Restarted Mozilla, deleted (using Profile Manager) all the profiles except my original one, and haven't see the mail problem since. But since the profile info had been all cocked up my proxy info was also incorrect, and it took me a while to figure that out (sometimes I'm not so bright). What I think might have happened is that I installed a nightly build (a week ago or more now) and that problem (no mail compose) showed up. So when I reinstalled an older version of Mozilla it didn't clear out the previous version -- I just paved over the old install. So it looks like the nightly build added a file the old installer didn't know about, and I live and learn. I appreciate your help with this, I now think the originial problem is in the nightly build, not v1.1 which is where I'm at right now. Maybe this weekend I will up date to the next nightly build, but maybe not... :) As to the profile loss problem I mentioned earlier, I didn't experience it fully or partially, some settings didn't transfer -- Proxy is the one that I remember, but I think I had to reset extentions (under advanced--systems tab) and the Tabbed Navigation settings, both where at their default levels. Thanks again. Have a good day. Robert
Ok sorry about the double post. RTH
using 20031003 I wasn't able to reproduce please try a more recent build if the bug is still there please reopen this bug
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.