User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; cs; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; cs; rv:1.9.2) Gecko/20100115 Firefox/3.6 In gmail I type text, click sent, go to sent folder, mail is not there, all I can see is empty message To: me, No subject. Check this Google forum for more info: http://www.google.com/support/forum/p/gmail/thread?tid=51cd56db6f35395b&hl=en Reproducible: Sometimes Steps to Reproduce: 1. As above. Always the same. Does not matter what configuration I use. 2. 3.
Uh, this sounds like a google issue. It could be an addon, so you can test with a new profile, http://support.mozilla.com/en-US/kb/Managing+profiles, but Google needs to help you with this. WFM with Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a3pre) Gecko/20100302 Minefield/3.7a3pre ID:20100302035357
Severity: critical → normal
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
OS: All → Windows 7
Resolution: --- → INVALID
Version: unspecified → 3.6 Branch
Please go to Tools/options/advanced/network/connection and set the proxy to "no proxy" instead of "automatic" and try it again.
Cant be Invalid when hundreds of people have problem. Makes no sense to learn so many people how to change their profile and many of them did with no change. And finally, it is not solely Gmail issue, it happened to some people on sites like Facebook. I changed my setting according to Mattis recommendation. If that helps I will close this discussion.
Status: RESOLVED → VERIFIED
Resolution: INVALID → WONTFIX
It helps only if you tell me the answer if disabling the proxy fixes your issue. In that case it would be a dupe of an already fixed form-posting bug.
Yes, I set according to your recommendation and informed everyone in Google forum to change it as well + report. Since the issue does happen only time to time we will see in one or two days whether your suggestion helped.
Status: VERIFIED → RESOLVED
Last Resolved: 9 years ago → 9 years ago
Resolution: WONTFIX → INVALID
Please see the report I posted at Google Support about this serious problem: http://www.google.com/support/forum/p/gmail/thread?fid=62eade6a6a781d9e00048277032b7246&hl=en The problem appears to lie with Firefox v3.6x, and it showed up directly after Google Buzz was introduced. Reverting to Firefox v3.5x stopped the problem from occurring (I made no other changes to my system), so it is definitely related to FFv3.6's relationship with Google. Has this bug been fixed, or does declaring it "INVALID" mean that Mozilla is simply ignoring the problem? I would obviously like to move back to FF v3.6 because v3.5x is so unstable!
>so it is definitely related to FFv3.6's relationship with Google. It's either a bug in the browser or a bug at google. >Has this bug been fixed, or does declaring it "INVALID" mean that Mozilla is >simply ignoring the problem? Read all comments including comment #4 And what do you mean with "mozilla" ? Tyler and I'm a part of the mozilla community, like you and if you look at the history https://bugzilla.mozilla.org/show_activity.cgi?id=549663 you will see that the reporter itself marked this bug as wontfix and tyler only corrected that to invalid. That would mean that the reporter ignores the bug.
Resolution: INVALID → DUPLICATE
Duplicate of bug: 547396
OK, thanks, so there's no information re resolving this I don't have already. RE comment # 4, i didn't change any settings when reverting to 3.5x - it is still on auto-detect and the problem is gone... and i'm afraid i'm not prepared to reinstall 3.6x and risk losing mails to give you that answer. :( i don't have the time. i merely wanted to know whether anyone had got to the bottom of the problem in 3.6x so that i could start using it again.
>RE comment # 4, i didn't change any settings when reverting to 3.5x - it is >still on auto-detect and the problem is gone... and i'm afraid i'm not prepared >to reinstall 3.6x and risk losing mails to give you that answer. :( i don't >have the time. How does it matter if it's gone in 3.5 with the same setting ? That is a step to find the reason for this issue. We have an existing bug in bugzilla that the reporter failed to find before filing this bug and you also didn't find. I know the other bug and to be sure that it's the same bug I just added the simple and easy test. The much more complicated way would be to create a http log that the reporter in bug 547396 did. That doesn't matter for you because I asked the reporter in comment #4 to do the test and he answered in comment #5 and confirmed that this "fixed" the issue. The bug was already marked wontfix/invalid at that time. I forget to dupe it after the reporter answered. The final answer is : This bug is already fixed. Fixed in bugzilla means that the bug is fixed in the soruce code and not that there is a new Firefox Version available for the users. But Mozilla released Firefox 3.6.2 which fixed a security issue and it also should fix this bug (but I might be wrong).
this is the resolved issue it is a duplicate of: https://bugzilla.mozilla.org/show_bug.cgi?id=542642
bug 547396 and bug 542642 are the same issue and both are dupes of bug 547239 but the developer want those bugs separate (unkown reason)
You need to log in before you can comment on or make changes to this bug.