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 768377 - Crash in _cancel_activation when dhcp4 lease expires
Crash in _cancel_activation when dhcp4 lease expires
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: IP and DNS config
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-07-04 14:32 UTC by Aron Xu
Modified: 2020-11-07 12:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aron Xu 2016-07-04 14:32:26 UTC 
Ubuntu error tracker receives several reports of crashes when the dhcp4 state is changed (NM_DHCP_STATE_EXPIRE).

+ Trace 236418

  • #0 _cancel_activation
    at devices/nm-device.c line 9990
  • #1 _set_state_full
    at devices/nm-device.c line 10657
  • #2 dhcp4_state_changed
    at devices/nm-device.c line 4589
  • #3 ffi_call_unix64
    at ../src/x86/unix64.S line 76
  • #4 ffi_call
    at ../src/x86/ffi64.c line 525
  • #5 g_cclosure_marshal_generic
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gclosure.c line 1490
  • #6 g_closure_invoke
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gclosure.c line 804
  • #7 signal_emit_unlocked_R
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3629
  • #8 g_signal_emit_valist
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3385
  • #9 g_signal_emit
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3441
  • #10 nm_dhcp_client_set_state
    at dhcp-manager/nm-dhcp-client.c line 330
  • #11 nm_dhcp_client_handle_event
    at dhcp-manager/nm-dhcp-client.c line 817
  • #12 ffi_call_unix64
    at ../src/x86/unix64.S line 76
  • #13 ffi_call
    at ../src/x86/ffi64.c line 525
  • #14 g_cclosure_marshal_generic
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gclosure.c line 1490
  • #15 g_closure_invoke
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gclosure.c line 804
  • #16 signal_emit_unlocked_R
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3629
  • #17 g_signal_emit_valist
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3395
  • #18 g_signal_emit
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3441
  • #19 handle_event
    at dhcp-manager/nm-dhcp-listener.c line 131
  • #20 emit_signal_instance_in_idle_cb
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gio/gdbusconnection.c line 3701
  • #21 g_main_dispatch
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c line 3154
  • #22 g_main_context_dispatch
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c line 3769
  • #23 g_main_context_iterate
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c line 3840
  • #24 g_main_loop_run
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c line 4034
  • #25 main
    at main.c line 477 






Comment 1


Thomas Haller





          2016-07-04 14:56:11 UTC
        



could you provide a logfile that shows the crash?

Which exact version of NM was used? Or is there a hyperlink to the downstream crashes?

Thanks.






Comment 2


Aron Xu





          2016-07-04 14:59:08 UTC
        



The version is 1.2.0, downstream link: https://bugs.launchpad.net/bugs/1598051






Comment 3


Beniamino Galvani





          2016-07-07 09:09:33 UTC
        



If there's a way to get logs at TRACE level, that probably would be very useful. From the stack trace it seems that in _set_state_full() there is initially a valid @self instance, but after the state change signal gets emitted the instance has been destroyed, probably in the call path of a signal handler. That should not happen as the NMManager should hold a reference to the device.






Comment 4


André Klapper





          2020-11-07 12:46:02 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!