- Mar 12, 2021
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
- Mar 11, 2021
-
-
Aleksander Morgado authored
(cherry picked from commit a772b706)
-
- Feb 26, 2021
-
-
Aleksander Morgado authored
g_assert() calls may be disabled, and if so, the network registration task would never get completed. (cherry picked from commit c7d36667)
-
- Feb 23, 2021
-
-
Aleksander Morgado authored
If we were requesting for IPv4v6 and we only got IPv4 reported as activated, we would right away ignore the IPv6 bits, even if we received IPv6 settings later on when querying for them. Change that, so that if an IP address of a given type is received, we assume the corresponding context was really activated even if the modem didn't report it in the connect set response. Fixes mobile-broadband/ModemManager#320 (cherry picked from commit a5462014)
-
- Jan 16, 2021
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Fixes mobile-broadband/ModemManager#306 Signed-off-by: Louis-Alexis Eyraud <louis-alexis.eyraud@sigfox.com> (cherry picked from commit 9c353cf6)
-
- Jan 13, 2021
-
-
Aleksander Morgado authored
See See mobile-broadband/ModemManager#302 (cherry picked from commit d12ab8a2)
-
Aleksander Morgado authored
The _get_port_gps() returns a full reference, use _peek_port_gps() instead. See mobile-broadband/ModemManager#302 (cherry picked from commit 102de14c)
-
This very peculiar case can happen when an intermediate initiliazition step of a modem fails. The ModemManager daemon should always expose the modem interface but let not assume that in mmcli and protect these calls. Signed-off-by: Frederic Martinsons <frederic.martinsons@sigfox.com> (cherry picked from commit 18b72a04)
-
On some modem (for example SORACOM SC-QGLC4-C1) , the character set setup step fails with "Unknown error" when the SIM card is missing or locked. This leads to not expose Modem interface and not being able to unlocked the SIM. We should not consider this step as fatal but just issue a warning to let other steps continue (which will let modem in failed state anyway). Closes #289 Signed-off-by: Frederic Martinsons <frederic.martinsons@sigfox.com> (cherry picked from commit 2f53a08e)
-
Aleksander Morgado authored
(cherry picked from commit 243272c1)
-
Aleksander Morgado authored
(cherry picked from commit ba4b3f60)
-
Aleksander Morgado authored
(cherry picked from commit 067b09c8)
-
- Dec 19, 2020
-
-
Aleksander Morgado authored
SAR service will be introduced in the stable libmbim 1.26.0, but it's been flagged in the dev 1.25.1 version already. (cherry picked from commit bee8a391)
-
Aleksander Morgado authored
(cherry picked from commit 0729ba5c)
-
- Dec 02, 2020
-
-
Aleksander Morgado authored
We had all the logic in place... but we were never actually enabling the signal strength indications because the `enable` flag in the context was never set. The bug was introduced back in May 2018, and released with 1.10.0. Fixes baefe53a (cherry picked from commit 12dd53a1)
-
- Nov 19, 2020
-
-
Fixes an issue where (5+8n)-character long SMS messages received on a CDMA network would be dropped with a "cannot read user data" error, while other length SMS messages would be delivered fine. Fix thanks to Peter Hunt (cherry picked from commit 7ac42e76)
-
- Nov 16, 2020
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
- Nov 09, 2020
-
-
Aleksander Morgado authored
Both 'physdev_subsystem' and 'interface_description' were leaking. (cherry picked from commit 37b3771e)
-
- Nov 08, 2020
-
-
Aleksander Morgado authored
The .actions file is generated by newer gtk-doc releases, we just treat it as e.g. the .signals or .types files. This is also already fixed in upstream gtk-doc: https://gitlab.gnome.org/GNOME/gtk-doc/-/merge_requests/61 (cherry picked from commit 50c69d54)
-
Aleksander Morgado authored
Fixes mobile-broadband/ModemManager#276 (cherry picked from commit 904adbfb)
-
Aleksander Morgado authored
The ModemManager-names.h header file is generated on git builds, and shipped within the release tarball, so treat it as a maintainer managed file that should only be removed on 'maintainer-clean'. This allows us to avoid requiring xsltproc to build release tarballs. (cherry picked from commit 3bda0562)
-
If multiple kernel device types inherit from MMKernerDevice, and those are compared against each other, the current logic returns TRUE if the G_OBJECT_TYPE of one of them is smaller than the other. This function is checking for equality, so returning FALSE is enough. (cherry picked from commit d7288861)
-
Aleksander Morgado authored
So that the list of ports shown in the Ports DBus property is also alphabetically sorted by port name, instead of having a mess like this: ----------------------------- System | device: qcom-soc | drivers: bam-dmux | plugin: qcom-soc | primary port: rpmsg0 | ports: rmnet5 (net), rmnet_usb0 (unknown), rmnet4 (net), | rpmsg1 (at), rmnet3 (net), rpmsg0 (qmi), rmnet2 (net), rmnet1 (net), | rmnet7 (net), rmnet0 (net), rmnet6 (net) (cherry picked from commit c3850319)
-
Aleksander Morgado authored
Running with G_DEBUG=fatal-warnings will end up reporting warning logs with G_LOG_FLAG_FATAL, which breaks our own logging logic. (cherry picked from commit a31d7622)
-
- Oct 21, 2020
-
-
Aleksander Morgado authored
If the modem goes away (ports removed) during the initialization phase (e.g. while QMI clients are being allocated), the MMPortQmi object will be closed and it will lose its internal QmiDevice. We should therefore consider the lack of QmiDevice a valid usecase in track_qmi_device_removed() and return a GError when that happens. #0 0x00007fb544618cc9 in raise () from /lib/libc.so.6 #1 0x00007fb54461bd68 in abort () from /lib/libc.so.6 #2 0x00007fb544e2213d in g_assertion_message () from /usr/lib/libglib-2.0.so.0 #3 0x00007fb544e221ba in g_assertion_message_expr () from /usr/lib/libglib-2.0.so.0 #4 0x00000000004be584 in track_qmi_device_removed () #5 0x00000000004be5e3 in allocate_next_client () #6 0x00000000004be7b1 in qmi_port_allocate_client_ready () #7 0x00007fb5453690a3 in g_task_return_now () from /usr/lib/libgio-2.0.so.0 #8 0x00007fb54536967e in g_task_return () from /usr/lib/libgio-2.0.so.0 #9 0x00000000004dd8f8 in allocate_client_ready () #10 0x00007fb5453690a3 in g_task_return_now () from /usr/lib/libgio-2.0.so.0 #11 0x00007fb54536967e in g_task_return () from /usr/lib/libgio-2.0.so.0 #12 0x00007fb54591d4de in allocate_cid_ready () from /usr/lib/libqmi-glib.so.5 ... (cherry picked from commit 8a54baa3)
-
Aleksander Morgado authored
(cherry picked from commit 1ed9f7e9)
-
- Oct 14, 2020
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
(cherry picked from commit f013e94f)
-
Aleksander Morgado authored
(cherry picked from commit 3b6176cb)
-
Aleksander Morgado authored
(cherry picked from commit 50c1550c)
-
Aleksander Morgado authored
(ModemManager:21568): GLib-WARNING **: 22:11:27.828: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: QMI protocol error (94): 'NotSupported' [21568]: <warn> [1582841487.829678] [modem0] couldn't load facility locks: (NULL) [21568]: <debug> [1582841487.830746] [modem0] loading UE mode of operation for EPS... [21568]: <debug> [1582841487.832138] [modem0/ttyUSB2/at] device open count is 2 (open) Segmentation fault This issue is only applicable in the mm-1-14 branch. Fixes cd686f10.
-
Aleksander Morgado authored
-