Description of problem: After upgrading my Lenovo ThinkPad X230 to Fedora 37 Beta, ModemManager crashes within seconds from starting. Since it runs as an auto-restarting systemd service, great amounts of coredumps accumulate. The exact position of the crash varies, but typical log output looks like this: $ sudo ModemManager ModemManager[25037]: <info> ModemManager (version 1.18.8-2.fc37) starting in system bus... ModemManager[25037]: [qrtr] socket lookup from 1:0 ModemManager[25037]: [qrtr] initial lookup finished ModemManager[25037]: opening device... ModemManager[25037]: [/dev/cdc-wdm2] Read max control message size from descriptors file: 512 ModemManager[25037]: <info> [cdc-wdm2/mbim] MBIM device is not QMI capable ModemManager[25037]: [/dev/cdc-wdm2] channel destroyed (ModemManager:25037): GLib-CRITICAL **: 23:31:42.842: g_regex_match_full: assertion 'regex != NULL' failed (ModemManager:25037): GLib-CRITICAL **: 23:31:42.843: g_regex_match_full: assertion 'regex != NULL' failed corrupted double-linked list Version-Release number of selected component (if applicable): 1.18.8-2.fc37 How reproducible: Always on my machine Steps to Reproduce: Boot and login, observe accumulating crashes with e.g. coredumpctl To reproduce manually: 1. sudo systemctl stop ModemManager.service 2. sudo ModemManager Actual results: Crash with error message "corrupted double-linked list" Expected results: No crash Additional info: Upstream issue: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/621 I can reproduce the issue with locally built ModemManager from upstream tag 1.18.8. Cherry-picking upstream fix in commit79a5a4ee fixes the issue in local build. I suggest it is cherry-picked to affected Fedora branches. According to discussion in upstream bug report, the trigger is glib2 version.
Some further information: I actually never use the laptop's modem. I initially noticed that there is something wrong with ModemManager because after the Fedora 37 Beta upgrade, I started receiving great amounts of SELinux denials of the following form: type=AVC msg=audit(1663963395.193:1911): avc: denied { execmem } for pid=14946 comm="ModemManager" scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:system_r:modemmanager_t:s0 tclass=process permissive=1 I believe that denial is triggered by ModemManager service crashing. I have not been able to reproduce it by manually running ModemManager.
Actually, it looks like just updating to the latest point release would fix the issue. The problem is mentioned as the very first item in 1.18.12 announcement: https://lists.freedesktop.org/archives/modemmanager-devel/2022-September/009419.html
*** Bug 2133733 has been marked as a duplicate of this bug. ***
Similar problem has been detected: At login with no user interaction reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/system.slice/ModemManager.service cmdline: /usr/sbin/ModemManager crash_function: g_malloc0 executable: /usr/sbin/ModemManager journald_cursor: s=5c6a9255d2a24d7c8b5e34079497078c;i=612b;b=1bd7c7e3fd804a27bdcab08402e0bc0c;m=26d298c;t=5eb8bbffb124d;x=dd935d6cff7ff96c kernel: 5.19.15-301.fc37.x86_64 package: ModemManager-1.18.8-2.fc37 reason: ModemManager killed by SIGABRT rootdir: / runlevel: unknown type: CCpp uid: 0
Created attachment 1919832 [details] File: backtrace
I second the suggestion from Comment #2: "updating to the latest point release would fix the issue" I have built the 1.8.12 from sources and it works (for me).
... addendum to Comment 6: on a PC, not using a laptop
As a work-around, I downgraded Glib2 to the last known working version, which is available from Koji. rpm -i --nodeps --force glib2-2.73.1-2.fc37.x86_64.rpm My internet connection works now, but note that doing this is inadvisable because it can break many other parts of your system.
Forget my previous comment, I clearly don't know what I'm talking about. ModemManager just happens to work sometimes. It's possible to initialize the modem by booting into another distribution that has a working ModemManager, and then reboot into Fedora. After that the connection seems to always work. Sleep mode messes it up.
Similar problem has been detected: Fedora 37 upgrade reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/system.slice/ModemManager.service cmdline: /usr/sbin/ModemManager crash_function: g_malloc0 executable: /usr/sbin/ModemManager journald_cursor: s=20c6f594adf44fdbb7e81e0b5e71d23a;i=e1e71;b=a7507338186046a5bb63a16a8952e762;m=e7986d6a;t=5eeb65e98b260;x=1bd2a27f144b1cce kernel: 6.0.10-300.fc37.x86_64 package: ModemManager-1.18.8-2.fc37 reason: ModemManager killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: This is a recurring problem which began once I installed a new cellular modem. I do not have any other information on what precipated the crash besides this. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/system.slice/ModemManager.service cmdline: /usr/sbin/ModemManager crash_function: g_malloc0 executable: /usr/sbin/ModemManager journald_cursor: s=5cbe6c533f974b1bb13b5989bdd3ba3d;i=33051;b=27fce7956fab40ecb10e6dec485abb9f;m=1bf4d9321;t=5efeb7c9d576e;x=9a39c268838e85f4 kernel: 6.0.12-300.fc37.x86_64 package: ModemManager-1.18.8-2.fc37 reason: ModemManager killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 0
Fixed for me with version ModemManager 1.18.12-1.fc37
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.