Re: assertion 'g_utf8_validate (string, -1, NULL)' failed
On Wed, Oct 21, 2015 at 2:00 PM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > >> >> Hi, I am working with Telit LE910. It works properly with ModemManager using >> QMI, but if I disable and enable the modem again, I get the following: >> >> root@ccimx6sbc:~# mmcli -m 0 -e >> >> ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: >> state changed (disabled -> enabling) >> >> ModemManager[698]: (ttyUSB2): port attributes not fully set >> >> ModemManager[698]: (ttyUSB3): port attributes not fully set >> >> ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: >> 3GPP Registration state changed (unknown -> registering) >> >> >> >> (ModemManager:698): GLib-CRITICAL **: g_variant_new_string: assertion >> 'g_utf8_validate (string, -1, NULL)' failed >> >> >> >> (ModemManager:698): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value >> != NULL' failed >> >> ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: >> 3GPP Registration state changed (registering -> home) >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (17): >> 'MissingArgument' >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (52): >> 'DeviceNotReady' >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): >> 'InvalidArgument' >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): >> 'InvalidArgument' >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (17): >> 'MissingArgument' >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (52): >> 'DeviceNotReady' >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): >> 'InvalidArgument' >> >> ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): >> 'InvalidArgument' >> >> ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: >> state changed (enabling -> registered) >> >> successfully enabled the modem >> >> >> Why are those asserts coming out? How can I fix those? > > Which ModemManager version is this? > > Can you MM with --debug to get full debug logs? See: > http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ > > I'd bet these are related to content of read SMS messages. Reporter replied privately. Looks like the problem is actually in the Operator name returned from the modem... >>>>>> TLV: >>>>>> type = "Current PLMN" (0x12) >>>>>> length = 15 >>>>>> value = D6:00:01:00:0A:F6:37:39:6C:7E:BB:CB:A0:E2:14 >>>>>> translated = [ mcc = '214' mnc = '1' description = '��~܋b' ] 21401 is Vodafone Spain, it should say something like "vodafone ES", not that garbage string. We may need to validate the incoming strings before using them; directly in libqmi. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
assertion 'g_utf8_validate (string, -1, NULL)' failed
Hi, I am working with Telit LE910. It works properly with ModemManager using QMI, but if I disable and enable the modem again, I get the following: root@ccimx6sbc:~# mmcli -m 0 -e ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling) ModemManager[698]: (ttyUSB2): port attributes not fully set ModemManager[698]: (ttyUSB3): port attributes not fully set ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering) (ModemManager:698): GLib-CRITICAL **: g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed (ModemManager:698): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != NULL' failed ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home) ModemManager[698]: Couldn't read SMS messages: QMI protocol error (17): 'MissingArgument' ModemManager[698]: Couldn't read SMS messages: QMI protocol error (52): 'DeviceNotReady' ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): 'InvalidArgument' ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): 'InvalidArgument' ModemManager[698]: Couldn't read SMS messages: QMI protocol error (17): 'MissingArgument' ModemManager[698]: Couldn't read SMS messages: QMI protocol error (52): 'DeviceNotReady' ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): 'InvalidArgument' ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): 'InvalidArgument' ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered) successfully enabled the modem Why are those asserts coming out? How can I fix those? ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: assertion 'g_utf8_validate (string, -1, NULL)' failed
Hey José, > > Hi, I am working with Telit LE910. It works properly with ModemManager using > QMI, but if I disable and enable the modem again, I get the following: > > root@ccimx6sbc:~# mmcli -m 0 -e > > ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: > state changed (disabled -> enabling) > > ModemManager[698]: (ttyUSB2): port attributes not fully set > > ModemManager[698]: (ttyUSB3): port attributes not fully set > > ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP > Registration state changed (unknown -> registering) > > > > (ModemManager:698): GLib-CRITICAL **: g_variant_new_string: assertion > 'g_utf8_validate (string, -1, NULL)' failed > > > > (ModemManager:698): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != > NULL' failed > > ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP > Registration state changed (registering -> home) > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (17): > 'MissingArgument' > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (52): > 'DeviceNotReady' > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): > 'InvalidArgument' > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): > 'InvalidArgument' > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (17): > 'MissingArgument' > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (52): > 'DeviceNotReady' > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): > 'InvalidArgument' > > ModemManager[698]: Couldn't read SMS messages: QMI protocol error (48): > 'InvalidArgument' > > ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0: > state changed (enabling -> registered) > > successfully enabled the modem > > > Why are those asserts coming out? How can I fix those? Which ModemManager version is this? Can you MM with --debug to get full debug logs? See: http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ I'd bet these are related to content of read SMS messages. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
