Closed Bug 869711 Opened 13 years ago Closed 13 years ago

Mail is not downloaded to the Reader

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mcepl, Unassigned)

Details

Attachments

(4 files)

I have managed to set up IMAP/SMTP (over SSL) for my own server. I see all my folders in the list, and when I open INBOX (or any other folder for that matter) I see the list of messages. Actually, what's even more interesting, I can see in the preview of the message even the first line of the body of the message. However, when I click on the message itself and I want to read it, Email app gets into something which looks like fetching of the body of the message (which is weird, because the preview seems to show that it has been downloaded already) and spinner never ends. Attached is a short movie showing the process (not very good I am afraid, I took it with my other phone). The server is Zarafa (zarafa-gateway-7.0.13-1.el6.i686 on RHEL-6 from EPEL packages). When this happens I see this in its logs: Tue May 7 18:14:30 2013: [13573] Accepted connection from 192.168.0.43 Tue May 7 18:14:30 2013: [13573] Starting worker process for IMAPs request Tue May 7 18:14:31 2013: [28877] IMAP Login from 192.168.0.43 for user matej Tue May 7 18:14:34 2013: [28727] Failed to read line: Connection reset by peer Tue May 7 18:14:34 2013: [28727] Client 192.168.0.43 thread exiting Not sure how to further debug that "Failed to read line".
If you could run an "adb logcat", that would be most useful. Specific commands to run can be found at https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo where there is also info about fancy structured debug log retrieval if that does not seem to do anything.
(In reply to Andrew Sutherland (:asuth) from comment #1) > If you could run an "adb logcat", that would be most useful. Specific > commands to run can be found at > https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo where there is also info > about fancy structured debug log retrieval if that does not seem to do > anything. Output of adb logcat is attached (I have finally make it working with my phone, great!). Rest from the RequiredBugInfo page: 1) The email address is matej@ceplovi.cz, server is luther.ceplovi.cz. 2) Using IMAP+SMTP account 3) output of adb logcat GeckoDump:V Gecko:V *:S. attached (but it seems to me that it is missing something ... I think I will attach full log as well, you can play with grep as well as I can, there doesn't seem to be any event in the filtered log when I open a message).
Also probably of interest is that the Email works perfectly well with the same configuration in r2d2b2g v.3.0 and that I use the latest update I got to Geeksphone Kean.
Thanks for the logcat! Indeed, I don't really see anything incriminating in there. Also, the secret log isn't something that will show up in the logcat. Instead, you would use the secret debug menu to cause a JSON file to be dumped to the device's internal storage and then provide that. In this case, I don't think it's really needed because... (In reply to Matej Cepl from comment #3) > Also probably of interest is that the Email works perfectly well with the > same configuration in r2d2b2g v.3.0 and that I use the latest update I got > to Geeksphone Kean. So, that sounds like the problem is with the Keon build then. It's my understanding that the keon at least shipped with a modified older build of one of the branches. Unfortunately, I am having real trouble finding any information about what build it might be using, etc. If you can map whatever build it's using to a specific commit in the gaia repo on one of the v1.0.1, v1-train, or master branches, I can help guess further, but my current guess is old build. (Or v1.0.1 build that doesn't have some fixes we have on v1-train and master.)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
(In reply to Andrew Sutherland (:asuth) from comment #5) > So, that sounds like the problem is with the Keon build then. It's my > understanding that the keon at least shipped with a modified older build of > one of the branches. Unfortunately, I am having real trouble finding any > information about what build it might be using, etc. If you can map > whatever build it's using to a specific commit in the gaia repo on one of > the v1.0.1, v1-train, or master branches, I can help guess further, but my > current guess is old build. (Or v1.0.1 build that doesn't have some fixes > we have on v1-train and master.) Does "Git commit info" (in "Device Information"/"More Information") 44915e2a1518 make sense?
"git branch -a --contains 44915e2a1518" is not giving me back anything useful, no.
(In reply to Andrew Sutherland (:asuth) from comment #7) > "git branch -a --contains 44915e2a1518" is not giving me back anything > useful, no. and sorry, the worst part of Geeksphone experience is that I cannot remember the name of my own phone. So, I have Peak, not Keon.
With the Geeksphone nightly build (http://downloads.geeksphone.com/peak_nightly/nightly-images-peak-2013-07-16.Gecko-d38f55b.Gaia-759f4b2.zip, build ID 20130703022357) I get exactly the same problem with Peak again. Further logs will be attached when I am able to collect them.
Status: RESOLVED → REOPENED
Flags: needinfo?(mcepl)
Resolution: WORKSFORME → ---
(In reply to Matěj Cepl from comment #9) > With the Geeksphone nightly build > (http://downloads.geeksphone.com/peak_nightly/nightly-images-peak-2013-07-16. > Gecko-d38f55b.Gaia-759f4b2.zip, build ID 20130703022357) I get exactly the > same problem with Peak again. Further logs will be attached when I am able > to collect them. Sorry, I have switched to v1.1 images from Geeksphone, because was too unusable (v1.1 is not that much better, but at least a little bit).
Flags: needinfo?(mcepl)
(In reply to Matěj Cepl from comment #10) > (In reply to Matěj Cepl from comment #9) > > With the Geeksphone nightly build > > (http://downloads.geeksphone.com/peak_nightly/nightly-images-peak-2013-07-16. > > Gecko-d38f55b.Gaia-759f4b2.zip, build ID 20130703022357) I get exactly the > > same problem with Peak again. Further logs will be attached when I am able > > to collect them. > > Sorry, I have switched to v1.1 images from Geeksphone, because was too > unusable (v1.1 is not that much better, but at least a little bit). Switched back to nightly, it seems to be really fixed.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: