[Touch-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2020-10-06 Thread Cyrille37
*** This bug is a duplicate of bug 1755305 *** https://bugs.launchpad.net/bugs/1755305 Hi, This bug continue, on Ubuntu 18.04.5 LTS + MATE 1.20.1. In .xsession-errors : (nm-applet:2221): Gtk-CRITICAL **: 12:09:29.609: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

[Touch-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2018-08-07 Thread kimo
*** This bug is a duplicate of bug 1755305 *** https://bugs.launchpad.net/bugs/1755305 ** This bug has been marked a duplicate of bug 1755305 .xsession-errors filled with entries -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2018-06-18 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2018-04-19 Thread Andrew
Is this the same as bug 1755305? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1751673 Title: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET

[Touch-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2018-02-26 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down