<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
Thanks for the answer Aleksander, by the way, I finally got a nano sim for my model and all went well. But, sadly same errors happens if the sim is locked (same error on CSCS than when the sim was missing). </div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
<br>
</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
I'll try at the beginning of next week to implement what you suggest on default encoding (by the way, what would be the best default: GSM, UTF8 ?) </div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
<br>
</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
Do you prefer that I issue one MR for mmcli protection about peek_modem and one for default charset? Or can I do both on the same MR? </div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
<br>
</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
Have a good week end! </div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Aleksander Morgado <aleksander@aleksander.es><br>
<b>Sent:</b> Saturday, December 19, 2020 10:40:32 AM<br>
<b>To:</b> Frederic Martinsons <frederic.martinsons@sigfox.com><br>
<b>Cc:</b> modemmanager-devel@lists.freedesktop.org <modemmanager-devel@lists.freedesktop.org><br>
<b>Subject:</b> Re: Modem SORACOM (SC-QGLC4-C1) : Unable to find a usable modem character set</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hey!<br>
<br>
><br>
> After a sim was inserted in the dongle, no problems have been notices so I it seems that a missing sim prevent modem initialization (which, to my opinion should not be , it should failed only on enable step).<br>
><br>
<br>
Yes, I agree. If the CSCS=X operation fails, we should still go on,<br>
maybe assuming a default charset encoding. For this specific setup,<br>
the modem will end up in failed state anyway, so it would be fine.<br>
<br>
> Nevertheless, I open a bug (<a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/289">https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/289</a>) to track the mmcli segfault on a badly initialized modem and I'll
try to come up with a MR to fix this (I don't know yet if the real fix should be to not expose the modem on DBus when it is not initialized or simply add a null-protection somewhere in mmcli)<br>
<br>
The real fix is in ModemManager daemon; it looks like the daemon is<br>
publishing a MM object in DBus, BUT which does NOT implement the<br>
"Modem" interface, and that is completely wrong. The MM objects in<br>
DBus must always implement the "Modem" interface. That said, yes,<br>
mmcli can also be improved so that we don't just assume the "Modem"<br>
interface always exists in the MM objects. If you're up to fixing<br>
this, the problem is that mmcli is assuming the return of<br>
mm_object_peek_modem() or mm_object_get_modem() is always non-NULL.<br>
<br>
-- <br>
Aleksander<br>
<a href="https://aleksander.es">https://aleksander.es</a><br>
</div>
</span></font></div>
</body>
</html>