Something is still not working quite right. Here's what mmsd is outputting at the end of the attachment download request:
When a mms comes in, mmsd outputs pages of "bytes read/[body] length" entries and then pauses for a good 30 seconds before popping up the final "bytes read 0". After that, the process continues to completion pretty quickly. The output reports a bit over 8K stored, and the file in ~/.mms/any matches the reported size.
On the Chatty side, the sms comes in immediately. A separate conversation is created with the "a mms has arrived, trying to d/l" message. After the mmsd long pause, 7 "file already exists" error messages pop up in the sms conversation. In ~/mms, an empty directory coded by date-time-sender is created for the mms that matches the Chatty error messages.
I'm not sure where the breakdown is happening. I spent some time tracing the debug output through the mmsd code and there is nothing obviously amiss on the mmsd side. It looks like mmsd is properly getting the download, but that long pause after the data chunks might be significant.
How does the handoff to purple-mms-sms work? Is purple creating the files in ~/mms from the raw files in ~/.mms/any?
Also, does mmsd output a logfile somewhere? Debug output for 8k of chunks has overwhelmed my ssh buffer.
Code:
.
.
bytes read 40
[body] length 40
bytes read 903
[body] length 903
bytes read 0
mmsd[14964]: src/service.c:web_get_cb() status: 200
mmsd[14964]: src/service.c:web_get_cb() data size = 833811
mmsd[14964]: src/service.c:web_get_cb() request->result_cb=0xaaaac94dc610 vs. retrieve_conf=0xaaaac94dc610/send_conf=0xaaaac94da6c0/notify_resp=0xaaaac94dd400
mmsd[14964]: src/store.c:generate_uuid_from_pdu() pdu 0xffffab720000 len 833811
mmsd[14964]: src/store.c:mms_store_file() pathname /home/manjaro/.mms/any/A0E4098838D985980D725864ED21EE07B8A92867
.
.On the Chatty side, the sms comes in immediately. A separate conversation is created with the "a mms has arrived, trying to d/l" message. After the mmsd long pause, 7 "file already exists" error messages pop up in the sms conversation. In ~/mms, an empty directory coded by date-time-sender is created for the mms that matches the Chatty error messages.
I'm not sure where the breakdown is happening. I spent some time tracing the debug output through the mmsd code and there is nothing obviously amiss on the mmsd side. It looks like mmsd is properly getting the download, but that long pause after the data chunks might be significant.
How does the handoff to purple-mms-sms work? Is purple creating the files in ~/mms from the raw files in ~/.mms/any?
Also, does mmsd output a logfile somewhere? Debug output for 8k of chunks has overwhelmed my ssh buffer.
