nm-applet assertion failure manipulating widgets
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
* Impact
the applet keeps logging gtk warnings
* Test case
Under xubuntu connect to a wifi, the journal shouldn't get nm-applet warnings
* Regression potential
The change is in the VPN submenu code, check that the items there are still correctly updated and available when needed
-------
nm-applet is logging a continuous stream of:
Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent
Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent
Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent
Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent
Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent
Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent
Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent
System updated on 19 Nov 2019
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-
ProcVersionSign
Uname: Linux 4.15.0-70-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Wed Nov 20 15:48:21 2019
InstallationDate: Installed on 2018-11-06 (379 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100
default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600
192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.24 metric 100
192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 metric 600
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: network-
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.10.14 connected started full enabled enabled enabled enabled enabled
Changed in network-manager-applet (Ubuntu): | |
status: | Incomplete → Fix Committed |
summary: |
- nm-applet assertion failure manipulatng widgets + nm-applet assertion failure manipulating widgets |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.