After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 684693 - GLib criticals during suspend/resume
GLib criticals during suspend/resume
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: ModemManager
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-09-24 02:59 UTC by Aleksander Morgado
Modified: 2012-10-08 08:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aleksander Morgado 2012-09-24 02:59:18 UTC 
Reported by Ben Chan in the mailing list:
https://mail.gnome.org/archives/networkmanager-list/2012-September/msg00218.html


While running suspend/resume stress tests on various modems, MM
gives a few glib assertion warnings.

(ModemManager:648): GLib-GIO-CRITICAL **:
g_dbus_connection_emit_signal: assertion `G_IS_DBUS_CONNECTION
(connection)' failed
(ModemManager:648): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
(ModemManager:648): GLib-GObject-CRITICAL **: g_object_unref:
assertion `G_IS_OBJECT (object)' failed


Backtraces:

GLib-GIO-CRITICAL **: g_dbus_connection_emit_signal: assertion
`G_IS_DBUS_CONNECTION (connection)' failed

+ Trace 230896

  • #0 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #1 g_dbus_connection_emit_signal
    from /usr/lib64/libgio-2.0.so.0
  • #2 _mm_gdbus_modem_location_emit_changed
    at mm-gdbus-modem.c line 8353
  • #3 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #4 ??
    from /usr/lib64/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #6 main
    at main.c line 150
  • #0 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #1 g_object_ref
    from /usr/lib64/libgobject-2.0.so.0
  • #2 disable
    at mm-broadband-modem.c line 7052
  • #3 handle_enable_auth_ready
    at mm-iface-modem.c line 1216
  • #4 g_simple_async_result_complete
    from /usr/lib64/libgio-2.0.so.0
  • #5 authorize_ready
    at mm-base-modem.c line 1015
  • #6 g_simple_async_result_complete
    from /usr/lib64/libgio-2.0.so.0
  • #7 ??
    from /usr/lib64/libgio-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #9 ??
    from /usr/lib64/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #11 main
    at main.c line 150
  • #0 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #1 disabling_context_complete_and_free
    at mm-broadband-modem.c line 6788
  • #2 handle_enable_auth_ready
    at mm-iface-modem.c line 1216
  • #3 g_simple_async_result_complete
    from /usr/lib64/libgio-2.0.so.0
  • #4 authorize_ready
    at mm-base-modem.c line 1015
  • #5 g_simple_async_result_complete
    from /usr/lib64/libgio-2.0.so.0
  • #6 ??
    from /usr/lib64/libgio-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #8 ??
    from /usr/lib64/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #10 main
    at main.c line 150 






Comment 1


Aleksander Morgado





          2012-10-08 08:44:26 UTC
        



I've fixed the issue triggering the last two criticals, fix is in git master now.

For the first critical, I've filled a new bug 685699 in glib/gdbus, as it may be an issue there. Will set this bug as fixed, and follow up in the new one if additional changes are needed in ModemManager.