Quote: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.From what you are describing, the breakdown is happening on the purple-mm-sms side. purple takes the raw files from mmsd (that are in the ~/.mms/any/ directory) and works on them in the function "pur_mmsd_receive_message()" (and puts them in ~/mms). The debug for purple-mm-sms (successful) looks similar to this:
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?
Code:
pur_mmsd_receive_message: New MMS at /org/ofono/mms/any/9D7B4C23EB3691E2A4C6EEF3260589E7446E425E
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:13.887: {'Status': <'received'>, 'Date': <'2021-01-05T06:41:06-0500'>, 'Subject': <'NoSubject'>, 'Sender': <'1xxxxxxxxxx'>, 'Recipients': <['+1yyyyyyyyyy']>, 'Attachments': <[('<image000000.jpg>', 'image/jpeg', '/home/mobian/.mms/any/9D7B4C23EB3691E2A4C6EEF3260589E7446E425E', uint64 501, uint64 60173)]>, 'Smil': <'<smil><head><layout><root-layout width="100%" height="100%"/><region id="Image" width="100%" height="100%" top="0%" left="0%" fit="meet"/></layout></head><body><par dur="5000ms"><img src="image000000.jpg" region="Image"/></par></body></smil>'>}
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:13.889: MMS Message Status: received
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:13.889: Recieved an MMS from someone else! Processing it....
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:14.100: ['+1yyyyyyyyyy']
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:14.100: [('<image000000.jpg>', 'image/jpeg', '/home/mobian/.mms/any/9D7B4C23EB3691E2A4C6EEF3260589E7446E425E', 501, 60173)]
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:14.110: modem_number: +1yyyyyyyyyy
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:14.110: You have 1 Recipients!
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:14.110: You only have one recipient! Posting MMS as IM.
(sm.puri.Chatty:2399): chatty-xeps-DEBUG: 06:41:14.111: Receiving msg on (nil) from +1xxxxxxxxxx with flags 2050
(sm.puri.Chatty:2399): chatty-manager-DEBUG: 06:41:14.139: Posting message id:(null) flags:2050 type:1 from:+1xxxxxxxxxx
** (sm.puri.Chatty:2399): DEBUG: 06:41:14.157: ../src/chatty-utils.c:83 number SMS
** (sm.puri.Chatty:2399): DEBUG: 06:41:14.182: ../src/chatty-utils.c:83 number +1xxxxxxxxxx
(sm.puri.Chatty:2399): mm-sms-DEBUG: 06:41:14.345: MMS delete finished
(06:41:19) util: Writing file blist.xml to directory /home/mobian/.purple
(06:41:19) util: Writing file /home/mobian/.purple/blist.xmlkYou may need to compile chatty with the debug options on to see the output there. I did it with
Code:
meson build -Db_sanitize=address -Dbuildtype=debugCode:
G_MESSAGES_DEBUG=all ./run --debug --verboseYou can also run pidgin with the debug options on with
Code:
G_MESSAGES_DEBUG=all pidginThat should help you with where the issue is on purple-mm-sms. Note that I have been able to run chatty over ssh (so itis easier to debug), and pidgin I cannot (so it's a bit more difficult to do.
Quote:Also, does mmsd output a logfile somewhere? Debug output for 8k of chunks has overwhelmed my ssh buffer.I am honestly not sure. I only started looking at mmsd to build an MM plugin. But I think your issue is in purple-mm-sms.
