Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBeniamino Galvani
2019-02-13 09:47:58 UTC
Description of problem:
Program received signal SIGABRT, Aborted.
0x00007efd39d18207 in raise () from /lib64/libc.so.6
(gdb) backtrace
#0 0x00007efd39d18207 in raise () at /lib64/libc.so.6
#1 0x00007efd39d198f8 in abort () at /lib64/libc.so.6
#2 0x00007efd3a33d665 in g_assertion_message () at /lib64/libglib-2.0.so.0
#3 0x00007efd3a33d6ca in g_assertion_message_expr () at /lib64/libglib-2.0.so.0
#4 0x000055c4bd90aac0 in cleanup_event_report_unsolicited_events (client=<optimized out>, indication_id=0x7efd300062ac, self=<optimized out>) at mm-bearer-qmi.c:973
#5 0x000055c4bd90ae2a in disconnect_context_step (ctx=0x55c4bf633aa0) at mm-bearer-qmi.c:1687
#6 0x000055c4bd8dfba3 in disconnect_auth_ready (self=<optimized out>, res=<optimized out>, ctx=0x55c4bf6359b0) at mm-iface-modem-simple.c:861
#7 0x00007efd3a8ac077 in g_simple_async_result_complete () at /lib64/libgio-2.0.so.0
#8 0x000055c4bd8c4061 in authorize_ready (authp=<optimized out>, res=<optimized out>, simple=0x7efd20009880) at mm-base-modem.c:1172
#9 0x00007efd3a8ac077 in g_simple_async_result_complete () at /lib64/libgio-2.0.so.0
#10 0x00007efd3a8ac0d9 in complete_in_idle_cb () at /lib64/libgio-2.0.so.0
#11 0x00007efd3a313c77 in g_idle_dispatch () at /lib64/libglib-2.0.so.0
#12 0x00007efd3a317049 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#13 0x00007efd3a3173a8 in g_main_context_iterate.isra.19 () at /lib64/libglib-2.0.so.0
#14 0x00007efd3a31767a in g_main_loop_run () at /lib64/libglib-2.0.so.0
#15 0x000055c4bd8b16cb in main (argc=<optimized out>, argv=<optimized out>) at main.c:181
(gdb) frame 4
#4 0x000055c4bd90aac0 in cleanup_event_report_unsolicited_events (client=<optimized out>, indication_id=0x7efd300062ac, self=<optimized out>) at mm-bearer-qmi.c:973
973 g_assert (*indication_id != 0);
(gdb)
Version-Release number of selected component (if applicable):
ModemManager-1.6.10-1
How reproducible:
sometimes
Steps to Reproduce:
nmcli connection up <wwan-connection> &
nmcli connection up <wwan-connection> &
nmcli connection up <wwan-connection> &
...
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2329