Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

[Moses Moore]

Ubuntu 18.10, network-manager-gnome 1.8.18-2

Every three minutes or less, the applet writes to stderr these messages:

(nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:3677): Gtk-WARNING **: 08:09:47.668: Can't set a parent on widget which has a parent
(nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:3677): Gtk-WARNING **: 08:10:50.639: Can't set a parent on widget which has a parent

Steps to reproduce:
 - install network-manager-gnome, add the nm-applet to the panel
 - wait

Expected outcome:
 - not filling up error logs

Seen outcome:
 - filling up error logs

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager-gnome 1.8.18-2ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Oct 22 08:08:37 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev enp5s0 proto dhcp metric 100
 169.254.0.0/16 dev enp5s0 scope link metric 1000
 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.111 metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (0 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME
 Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b ethernet 1540209985 Mon 22 Oct 2018 08:06:25 AM EDT yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 enp5s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b /org/freedesktop/NetworkManager/ActiveConnection/1
 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.12.4 connected started full enabled enabled enabled enabled disabled

[Sebastien Bacher (seb128)]

The report is from XFCE, would be useful to get a gdb backtrace from the warning if you could (https://wiki.ubuntu.com/DebuggingProgramCrash)

[Moses Moore (moses-ubuntu)]

The wiki page says to look in /var/crash but there's no files there. it says to install the "$name-dbg" package, but there is no "network-manager-gnome-dbg" package.

I added the ddebs repository, and installed `apt-get install network-manager-gnome-dbgsym=1.8.18-2ubuntu2` . Then I went to https://wiki.ubuntu.com/Backtrace and followed the instructions there to get a "backtrace". attaching it now.

[Launchpad Janitor (janitor)]

[Expired for network-manager-applet (Ubuntu) because there has been no activity for 60 days.]

[Andrej Shadura (andrew.sh)]

Since it’s not a crash, it’d be difficult to get traces. The issue is in the patch Ubuntu ships for the indicator menu; the warnings don’t appear when the indicator menu is not used.

[Sebastien Bacher (seb128)]

You can get a backtrace of warnings either by using --g-fatal-warnings (but then it only works until the first warning since it exits) or by setting a break on g_log in gdb

[Moses Moore (moses-ubuntu)]

I've upgraded to 19.04 since, with network-manager-gnome 1.8.20-1ubuntu1 . It bleats some error messages to stderr on startup, but not a constant stream like before:

(nm-applet:13762): Gtk-WARNING **: 22:45:40.305: Can't set a parent on widget which has a parent
(nm-applet:13762): Gdk-CRITICAL **: 22:45:40.569: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(nm-applet:13762): Gtk-CRITICAL **: 22:45:41.561: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:13762): Gtk-CRITICAL **: 22:45:41.561: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:13762): Gtk-WARNING **: 22:45:41.572: Can't set a parent on widget which has a parent
(nm-applet:13762): Gtk-CRITICAL **: 22:45:41.582: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:13762): Gtk-CRITICAL **: 22:45:41.582: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(nm-applet:13762): Gtk-WARNING **: 22:45:41.595: Can't set a parent on widget which has a parent

Running it with "--g-fatal-warnings" as you suggested just quits on the first warning, no crash, no dump:

moses@jolyne:~$ nm-applet --g-fatal-warnings
(nm-applet:13783): Gtk-WARNING **: 22:47:37.548: Can't set a parent on widget which has a parent
Trace/breakpoint trap

Attaching a new backtrace. (I attached a backtrace last time, but this bug was still marked "incomplete" and autocleaned. If this was because I was non-compliant, please tell me what I did or have done wrong.)

[Moses Moore (moses-ubuntu)]

My mistake, stderr *is* getting a constant repeat of these error messages in version 1.8.20-1ubuntu1 , I didn't wait long enough. The same six warning messages, every 60-120 seconds.

[Sebastien Bacher (seb128)]

> quits on the first warning, no crash, no dump:

the backtrace you got seems right, but it's not really useful without libglib2.0-0-dbgsym libgtk-3-0-dbgsym and network-manager-dbgsym (and possibly the libnm ones as well)

I'm setting back to New, it seems a real issue but it doesn't impact our default desktop/GNOME so it's low priority for us to debug

[Moses Moore (moses-ubuntu)]

As per https://wiki.ubuntu.com/DebuggingProgramCrash I added the ddebs repositories

echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse" >> /etc/apt/sources.list.d/ddebs.list
echo -e "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse\ndeb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" >> /etc/apt/sources.list.d/ddebs.list
apt install ubuntu-dbgsym-keyring
apt update

Then for each of the packages you mentioned, I need to run "apt-cache policy $name", write down the version number in "Installled" then "apt install ${name}-dbgsym=${version}" for each one. (I hope I don't need to do this for all 84 libraries linked by nm-applet.)

dpkg -S `which nm-applet`
apt install network-manager-gnome-dbgsym=1.8.20-1ubuntu1

ldd `which nm-applet` |egrep 'libglib|libgtk|network-manager'

dpkg -S /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
apt-cache policy libgtk-3-0
apt install libgtk-3-0-dbgsym=3.24.8-1ubuntu1

dpkg -S /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
apt-cache policy libglib2.0-0
apt install libglib2.0-0-dbgsym=2.60.0-1

Then following the instructions in https://wiki.ubuntu.com/Backtrace again. New backtrace is attached to this comment.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[oldfred (oldfred)]

Posts twice about every 10 seconds.

fred@fred-Z170N-focal:~$ echo $DESKTOP_SESSION
gnome-flashback-metacity
fred@fred-Z170N-focal:~$ gnome-shell --version
GNOME Shell 3.34.3
fred@fred-Z170N-focal:~$ lsb_release -d
Description: Ubuntu Focal Fossa (development branch)

Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: Can't set a parent on widget which has a parent
Feb 9 11:13:41 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Feb 9 11:13:41 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed