purple-mm-sms issueshttps://source.puri.sm/Librem5/purple-mm-sms/-/issues2021-07-04T12:59:30Zhttps://source.puri.sm/Librem5/purple-mm-sms/-/issues/24Mismatch between license headers and debian/copyright2021-07-04T12:59:30ZJan TojnarMismatch between license headers and debian/copyright[mm-sms.c](https://source.puri.sm/Librem5/purple-mm-sms/-/blob/b4b7e4c1beb7e1b8a019dffcc71ca1f5fbff91e9/mm-sms.c#L5-7) and [itu-e212-iso.h](https://source.puri.sm/Librem5/purple-mm-sms/-/blob/b4b7e4c1beb7e1b8a019dffcc71ca1f5fbff91e9/itu-...[mm-sms.c](https://source.puri.sm/Librem5/purple-mm-sms/-/blob/b4b7e4c1beb7e1b8a019dffcc71ca1f5fbff91e9/mm-sms.c#L5-7) and [itu-e212-iso.h](https://source.puri.sm/Librem5/purple-mm-sms/-/blob/b4b7e4c1beb7e1b8a019dffcc71ca1f5fbff91e9/itu-e212-iso.h#L11) declare `GPL-2.0-or-later` in the blurb but [debian/copyright](https://source.puri.sm/Librem5/purple-mm-sms/-/blob/b4b7e4c1beb7e1b8a019dffcc71ca1f5fbff91e9/debian/copyright#L7) says `GPL-3.0-or-later`.https://source.puri.sm/Librem5/purple-mm-sms/-/issues/23Segmentation fault in `device_match_by_obejct`2021-03-04T09:49:43ZGuido GuntherSegmentation fault in `device_match_by_obejct`Chatty crashes a lot like
```
(gdb) bt
#0 0x0000ffff6e79f644 in device_match_by_object (device=0x100000002, object=0xffff680065b0) at mm-sms.c:770
#1 0x0000ffff8e32b9c4 in g_ptr_array_find_with_equal_func (haystack=0xaaaaef761920, nee...Chatty crashes a lot like
```
(gdb) bt
#0 0x0000ffff6e79f644 in device_match_by_object (device=0x100000002, object=0xffff680065b0) at mm-sms.c:770
#1 0x0000ffff8e32b9c4 in g_ptr_array_find_with_equal_func (haystack=0xaaaaef761920, needle=0xffff680065b0, equal_func=0xffff6e79f594 <device_match_by_object>, index_=0xffffcec57e34)
at ../../../glib/garray.c:2162
#2 0x0000ffff6e79fa10 in cb_object_removed (manager=0xaaaaefca8300, object=0xffff680065b0, user_data=0x0) at mm-sms.c:843
#6 0x0000ffff8e47c098 in <emit signal 0xffff8e64c258 "object-removed" on instance 0xaaaaefca8300 [MMManager]>
(instance=instance@entry=0xaaaaefca8300, detailed_signal=detailed_signal@entry=0xffff8e64c258 "object-removed") at ../../../gobject/gsignal.c:3591
#3 0x0000ffff8e462018 in g_closure_invoke
(closure=0xaaaaef5bce30, return_value=return_value@entry=0x0, n_param_values=2, param_values=param_values@entry=0xffffcec58020, invocation_hint=invocation_hint@entry=0xffffcec57fe8)
at ../../../gobject/gclosure.c:810
#4 0x0000ffff8e4759e4 in signal_emit_unlocked_R
(node=node@entry=0xffff74001790, detail=detail@entry=0, instance=instance@entry=0xaaaaefca8300, emission_return=emission_return@entry=0x0, instance_and_params=0xffffcec58020, instance_and_params@entry=0x0)
at ../../../gobject/gsignal.c:3739
#5 0x0000ffff8e47b898 in g_signal_emit_valist (instance=instance@entry=0xaaaaefca8300, signal_id=signal_id@entry=42, detail=detail@entry=0, var_args=...) at ../../../gobject/gsignal.c:3495
#7 0x0000ffff8e5fb19c in remove_interfaces (interface_names=0xaaaaef5c0a90, object_path=0xaaaaef5696b0 "/org/freedesktop/ModemManager1/Modem/6", manager=0xaaaaefca8300 [MMManager])
at ../../../gio/gdbusobjectmanagerclient.c:1665
#8 on_control_proxy_g_signal (proxy=<optimized out>, sender_name=<optimized out>, signal_name=<optimized out>, parameters=<optimized out>, user_data=<optimized out>)
at ../../../gio/gdbusobjectmanagerclient.c:1749
#12 0x0000ffff8e47be90 in <emit signal ??? on instance 0xaaaaefb912d0 [GDBusProxy]> (instance=instance@entry=0xaaaaefb912d0, signal_id=<optimized out>, detail=detail@entry=0) at ../../../gobject/gsignal.c:3551
#9 0x0000ffff8e462018 in g_closure_invoke
(closure=0xffff680077e0, return_value=return_value@entry=0x0, n_param_values=4, param_values=param_values@entry=0xffffcec58560, invocation_hint=invocation_hint@entry=0xffffcec58528)
at ../../../gobject/gclosure.c:810
#10 0x0000ffff8e4759e4 in signal_emit_unlocked_R
(node=node@entry=0xaaaaef536720, detail=detail@entry=0, instance=instance@entry=0xaaaaefb912d0, emission_return=emission_return@entry=0x0, instance_and_params=0xffffcec58560, instance_and_params@entry=0x0)
at ../../../gobject/gsignal.c:3739
#11 0x0000ffff8e47b898 in g_signal_emit_valist (instance=instance@entry=0xaaaaefb912d0, signal_id=<optimized out>, detail=detail@entry=0, var_args=...) at ../../../gobject/gsignal.c:3495
#13 0x0000ffff8e5e9f90 in on_signal_received
(connection=<optimized out>, sender_name=0xffff7802f9b0 ":1.12", object_path=<optimized out>, interface_name=<optimized out>, signal_name=0xffff78021910 "InterfacesRemoved", parameters=0xffff7803c500, user_data=<optimized out>) at ../../../gio/gdbusproxy.c:884
#14 0x0000ffff8e5d63c8 in emit_signal_instance_in_idle_cb (data=0xffff7803cba0) at ../../../gio/gdbusconnection.c:3789
#15 0x0000ffff8e35dab4 in g_main_dispatch (context=0xaaaaef529a40) at ../../../glib/gmain.c:3325
#16 g_main_context_dispatch (context=0xaaaaef529a40) at ../../../glib/gmain.c:4043
#17 0x0000ffff8e35de5c in g_main_context_iterate (context=context@entry=0xaaaaef529a40, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4119
#18 0x0000ffff8e35df24 in g_main_context_iteration (context=context@entry=0xaaaaef529a40, may_block=may_block@entry=1) at ../../../glib/gmain.c:4184
#19 0x0000ffff8e5abac8 in g_application_run (application=0xaaaaef528100 [ChattyApplication], argc=<optimized out>, argv=0xffffcec58bb8) at ../../../gio/gapplication.c:2559
#20 0x0000aaaabca877c8 in main ()
```
on byzantium (
This happens up to point where `gnome-session` gives up and one doesn't have chatty running and hence misses SMS, etc. hence flagging as important.
```
# dpkg -s purple-mm-sms
Package: purple-mm-sms
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 73
Maintainer: DebianOnMobile Maintainers <debian-on-mobile-maintainers@alioth-lists.debian.net>
Architecture: arm64
Version: 0.1.7-1
Depends: libc6 (>= 2.17), libglib2.0-0 (>= 2.53.2), libmm-glib0 (>= 1.7.990), libpurple0 (>= 2.6.0), modemmanager
Description: libpurple plugin for SMS
Plugin for libpurple which adds the ability to communicate via
SMS using ModemManager.
Homepage: https://source.puri.sm/Librem5/purple-mm-sms
```https://source.puri.sm/Librem5/purple-mm-sms/-/issues/22Chatty stops receiving SMS after sending an SMS2021-01-11T20:17:59ZGergely HorváthChatty stops receiving SMS after sending an SMSThis issue was first published as https://gitlab.com/mobian1/issues/-/issues/215 and later on https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/299. On the MM page it seemed that we triangled the problem to Chatty. He...This issue was first published as https://gitlab.com/mobian1/issues/-/issues/215 and later on https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/299. On the MM page it seemed that we triangled the problem to Chatty. Here are my experiences:
I'm on Mobian+Phosh on PinePhone, latest version as of 2021-01-04 (just did apt update && apt upgrade). *Update*: system was updated on 2021-01-10. Receiving SMS is unreliable. I'm using a T-Mobile SIM in Hungary. Mobile setting currently is 2g/3g/4g (4g preferred). 2g only, 3g only, 4g only, 3g/4g (pref:4g) was also tested.
**Actual problem:**
The problem after some debugging (see in the ModemManager issue) seems to be that after sending an SMS from Chatty, it is unable to receive more. These issues does not surface when Chatty is killed. I could reproduce the issue anytime by sending an SMS (or more) from another phone, replying to it, and no more SMS arrives. I tried sending SMS from other numbers as well (bank 2FA) with the same result. When Chatty was shut down, sending has no effect on receiving the SMS messages.
No MMS were sent from the phone and to be fair I haven't received one in years.
Thanks in advance for looking into it!
Gergelyhttps://source.puri.sm/Librem5/purple-mm-sms/-/issues/21Must only remove SMS it created itself2021-01-08T13:41:33ZGuido GuntherMust only remove SMS it created itselfSeems chatty removes SMS created via mmcli from the modem as well, see: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/294#note_749979Seems chatty removes SMS created via mmcli from the modem as well, see: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/294#note_749979https://source.puri.sm/Librem5/purple-mm-sms/-/issues/20Support MMS2021-01-05T02:27:29ZTim M.Support MMSchatty#30 is for MMS support in chatty.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/257 is for ModemManager.
Before chatty#30 can be solved (or as part of solving that), we will need MMS support here in the con...chatty#30 is for MMS support in chatty.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/257 is for ModemManager.
Before chatty#30 can be solved (or as part of solving that), we will need MMS support here in the connector.
Also, it seems to me that most of the work will be here, not in ModemManager, just as mmsd handles MMS on ofono based phones.https://source.puri.sm/Librem5/purple-mm-sms/-/issues/19include LICENSE file in sources2020-09-27T20:25:13ZNikhil Jhainclude LICENSE file in sourcesthis is required for packaging in many distributions, and is just common practicethis is required for packaging in many distributions, and is just common practicehttps://source.puri.sm/Librem5/purple-mm-sms/-/issues/18cross compilation support2020-09-20T04:42:51ZJulio Galvancross compilation supportI am trying to package this library to VoidLinux but it fails to cross compile. I don't know a lot about `make` but I do use `meson` and I have put together this patch and hope it is useful. It is missing a few things but I hope someone ...I am trying to package this library to VoidLinux but it fails to cross compile. I don't know a lot about `make` but I do use `meson` and I have put together this patch and hope it is useful. It is missing a few things but I hope someone else can make it better.
```
meson.build | 42 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
create mode 100644 meson.build
diff --git a/meson.build b/meson.build
new file mode 100644
index 0000000..8b6c90e
--- /dev/null
+++ b/meson.build
@@ -0,0 +1,42 @@
+project('purple-mm-sms', 'c',
+ version: '0.1.7',
+)
+
+cc = meson.get_compiler('c')
+
+purple = dependency('purple')
+mm = dependency('mm-glib')
+glib= dependency('glib-2.0', version: '>=2.50.0')
+
+purple_plugdir = purple.get_pkgconfig_variable('plugindir')
+
+mm_sms_headers = [
+ 'mm-sms.h',
+ 'itu-e212-iso.h',
+]
+
+mm_sms_sources = [
+ mm_sms_headers,
+ 'mm-sms.c',
+]
+
+mm_sms_deps = [
+ purple,
+ mm,
+ glib,
+]
+
+mm_sms_shared = shared_library(
+ 'mm-sms',
+ mm_sms_sources,
+ dependencies : mm_sms_deps,
+ name_prefix : '',
+ install_dir : purple_plugdir,
+ install : true,
+)
+
+
+iconsdir = join_paths(get_option('datadir'), 'pixmaps', 'pidgin', 'protocols')
+foreach size: ['16', '22', '48']
+ install_data('icons/mm-sms-' + size + 'px.png', rename: 'mm-sms.png', install_dir: iconsdir + '/' + size)
+endforeach
--
2.28.0
```https://source.puri.sm/Librem5/purple-mm-sms/-/issues/17Duplicate messages when remove recieved messages is off2020-08-24T18:50:20ZAren MoynihanDuplicate messages when remove recieved messages is offWhen removing received sms messages is set to off via `/mm-sms rm_r off` purple-mm-sms duplicates messages that have already been received.
This seems to happen when purple-mm-sms polls ModemManager for messages (I believe this happens ...When removing received sms messages is set to off via `/mm-sms rm_r off` purple-mm-sms duplicates messages that have already been received.
This seems to happen when purple-mm-sms polls ModemManager for messages (I believe this happens when it starts up). I'm guessing purple-mm-sms gets a full list of messages and doesn't check for duplicates of messages it already knows about.
I think this may be related to chatty#287, but it's not quite the same bug.https://source.puri.sm/Librem5/purple-mm-sms/-/issues/16Sending a message fails silently on polkit authorization error2020-07-08T00:15:03ZSebastian KrzyszkowiakSending a message fails silently on polkit authorization errorI tried to send an SMS after running Chatty from ssh console, which resulted in PolicyKit error. However, the UI didn't indicate it in any way and I had to check the log in order to see why the other end haven't received an expected mess...I tried to send an SMS after running Chatty from ssh console, which resulted in PolicyKit error. However, the UI didn't indicate it in any way and I had to check the log in order to see why the other end haven't received an expected message:
```
(sm.puri.Chatty:2421): mm-sms-DEBUG: 02:05:48.669: Couldn't create new SMS - error: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unauthorized: PolicyKit authorization failed: not authorized for 'org.freedesktop.ModemManager1.Messaging'
```https://source.puri.sm/Librem5/purple-mm-sms/-/issues/15Incoming SMS not handled, PDU type "cdma-deliver"2020-10-02T07:39:33ZSalem ElrahalIncoming SMS not handled, PDU type "cdma-deliver"I have a 4G connection with Verizon in US, am getting the following logs and no SMS message in chatty:
```
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.247: pur_mm_get_new_sms path /org/freedesktop/ModemManager1/SMS/10
(sm.puri.Chatty:...I have a 4G connection with Verizon in US, am getting the following logs and no SMS message in chatty:
```
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.247: pur_mm_get_new_sms path /org/freedesktop/ModemManager1/SMS/10
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.247: cb_dbus_signal_sms_added: New SMS at /org/freedesktop/ModemManager1/SMS/10
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.306: PDU type not handled
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.307: pur_mm_check_pdu_type: pdu type cdma-deliver
(sm.puri.Chatty:3037): mm-sms-DEBUG: 12:34:21.307: cb_sms_list_new_ready
```
I guess this PDU type is not mapped/supported here:
https://source.puri.sm/Librem5/purple-mm-sms/-/blob/master/mm-sms.c#L585https://source.puri.sm/Librem5/purple-mm-sms/-/issues/11Pidgin crash after send or receive a sms2020-04-06T05:50:02ZViktor Ivan Rodriguez AbdalaPidgin crash after send or receive a smsHi, when I receive a new sms the pidgin application close suddenly, I start again pidgin and ask for root password for each sms received, if a have 15 sms I need to write 15 times the root password, and when I write a new sms then pidgin...Hi, when I receive a new sms the pidgin application close suddenly, I start again pidgin and ask for root password for each sms received, if a have 15 sms I need to write 15 times the root password, and when I write a new sms then pidgin close again.https://source.puri.sm/Librem5/purple-mm-sms/-/issues/8Improve SMS Plugin Functionality2019-07-24T15:14:55ZAndrea SchaeferImprove SMS Plugin Functionality- [x] Improve plugin startup (plugin/modem initialization)
- [x] Improve modem state handler (will potentially fix https://source.puri.sm/Librem5/chatty/issues/138)
- [x] Add an API function to provide MODEM status (will resolve https://...- [x] Improve plugin startup (plugin/modem initialization)
- [x] Improve modem state handler (will potentially fix https://source.puri.sm/Librem5/chatty/issues/138)
- [x] Add an API function to provide MODEM status (will resolve https://source.puri.sm/Librem5/chatty/issues/94)
- [x] Add support for multipart SMS (will close https://source.puri.sm/Librem5/purple-mm-sms/issues/10)
- [x] Evaluate delivery reports and add API function (will close https://source.puri.sm/Librem5/chatty/issues/65)
- [x] Improve message-acknowledge handling
- [x] Fix smiley issue - libmm->mm_sms_get_text is limited to UTF-8 (will resolve https://source.puri.sm/Librem5/chatty/issues/136 and https://source.puri.sm/Librem5/chatty/issues/139)Last: Iris (W28-30)Andrea SchaeferAndrea Schaeferhttps://source.puri.sm/Librem5/purple-mm-sms/-/issues/7Add signal for modem status2019-05-16T09:29:05ZAndrea SchaeferAdd signal for modem statusEmit a signal to inform Chatty about the modem status (like messaging capabilities available, SIM status, etc.)Emit a signal to inform Chatty about the modem status (like messaging capabilities available, SIM status, etc.)https://source.puri.sm/Librem5/purple-mm-sms/-/issues/3Support binary data2018-10-19T12:50:40ZAndrea SchaeferSupport binary dataTry to get binary data if a text message isn't decodedTry to get binary data if a text message isn't decodedhttps://source.puri.sm/Librem5/purple-mm-sms/-/issues/1Support delivery reports2018-10-19T11:57:42ZAndrea SchaeferSupport delivery reports