Version-Release number of selected component: NetworkManager-0.9.9.0-38.git20131003.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: rdisc_config_changed executable: /usr/sbin/NetworkManager kernel: 3.14.1-200.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (5 frames) #0 rdisc_config_changed at devices/nm-device.c:3288 #1 g_cclosure_marshal_VOID__INT at gmarshal.c:372 #5 g_signal_emit_by_name at gsignal.c:3426 #6 check_timestamps at rdisc/nm-lndp-rdisc.c:380 #7 timeout_cb at rdisc/nm-lndp-rdisc.c:403
Created attachment 890926 [details] File: backtrace
Created attachment 890927 [details] File: cgroup
Created attachment 890928 [details] File: core_backtrace
Created attachment 890929 [details] File: dso_list
Created attachment 890930 [details] File: environ
Created attachment 890931 [details] File: exploitable
Created attachment 890932 [details] File: limits
Created attachment 890933 [details] File: maps
Created attachment 890934 [details] File: open_fds
Created attachment 890935 [details] File: proc_pid_status
Created attachment 890936 [details] File: var_log_messages
avril 29 22:25:44 localhost.localdomain NetworkManager[770]: (NetworkManager:770): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed rdisc_config_changed (NMRDisc *rdisc, NMRDiscConfigMap changed, NMDevice *device) { NMDevicePrivate *priv = NM_DEVICE_GET_PRIVATE (device); Getting private structure of NMDevice fails, so 'device' object seems to be invalid. However it seems that the code correctly disconnects rdisc_config_changed() handler in NMDevice::dispose(). Patrick, are you able to reproduce the crash or it was just a random issue?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.