On Mon, 2017-05-15 at 21:33 -0400, A. F. Cano wrote:
On Sat, May 13, 2017 at 04:47:56PM -0400, A. F. Cano wrote:On Wed, May 10, 2017 at 02:21:07PM -0400, I wrote:I have encountered this the last time I connected. The ppp connection was working fine but this message kept repeating the whole time the connection was up: May 9 21:02:06 fbx NetworkManager[379]: g_signal_emit_valist: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed ...But now these messages have stopped. These packages have been recently upgraded, so it's possible that a bug was fixed in one of them. 2017-05-13 06:39:04,329 INFO Packages that will be upgraded: file gcc-6-base init init-system-helpers initramfs-tools initramfs- tools-core iso-codes libfreetype6 libgcc1 libgomp1 libmagic-mgc libmagic1 libnss-myhostname libpam-systemd libstdc++6 libsystemd0 libudev1 ntp ssl-cert systemd systemd-sysv udev Or maybe not and it's some non-repeatable trigger, but the backtrace previously supplied seemed to point to a lot of libraries.This seems to be more random than I hoped. The g_signal_emit_valist messages are back... May 15 21:28:10 fbx NetworkManager[31616]: instance with invalid (NULL) class pointer May 15 21:28:10 fbx NetworkManager[31616]: g_signal_emit_valist: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 15 21:28:15 fbx NetworkManager[31616]: instance with invalid (NULL) class pointer May 15 21:28:15 fbx NetworkManager[31616]: g_signal_emit_valist: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed But this time with a NULL class pointer, so it appears that further checks are being made.
Hi, These are bugs. If you set G_DEBUG=fatal-criticals, then glib will core-dump for such assertion failures. You can also set [main] debug+=fatal-warnings in NetworkManager.conf Make sure to install debugging symbols, and get a backtrace. It might be simpliest to run NM under gdb (with --debug to keep it in forground). best, Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part