gtk_widget_destroy reports error

Thank you for your bug report, but how is that a bug in the network indicator? Also you didn't attach the example you mentioned?

Apologies for the mess up. I was looking at a similar bug listed for the network applet. I thought I had changed it, but the first time I tried to save I had a timeout and had to re-enter the details all over. Somehow the network applet must have been set when I re-entered. It was meant to a problem with Gtk+3.0 Dev.
Sample code to reproduced is attached.

The original package noted was a mistake. The nearest I can guess at for this problem is as above. I couldn't find anything that was obvious for a problem Gtk+3.0 development

Looking upstream it seems similar to https://gitlab.gnome.org/GNOME/gtk/issues/125 , the warning is indeed fixed in the current Ubuntu serie, could be a candidate to include if we do a SRU update for gtk but doesn't seem an high importance one/probably not worth an update by itself

It certainly does look related and absolutely agree that its not really
a high priority.

Thanks. Regards.

On 19/2/19 2:20 am, Sebastien Bacher wrote:
> Looking upstream it seems similar to
> https://gitlab.gnome.org/GNOME/gtk/issues/125 , the warning is indeed
> fixed in the current Ubuntu serie, could be a candidate to include if we
> do a SRU update for gtk but doesn't seem an high importance one/probably
> not worth an update by itself
>
>
> ** Package changed: libcanberra (Ubuntu) => gtk+3.0 (Ubuntu)
>
> ** Changed in: gtk+3.0 (Ubuntu)
> Status: Incomplete => Fix Released
>

I'm updating the bug to be SRU compliant and staging in the vcs, not going to do an upload for that but it's queued to be included next time we do one

Hello Anthony, or anyone else affected,

Accepted gtk+3.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.30-1ubuntu3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Using the current bionic-updates version the warning is displayed, after upgrading to 3.22.30-1ubuntu3 clicking the button works without any warning display, the fix is verified

This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu3

---------------
gtk+3.0 (3.22.30-1ubuntu3) bionic; urgency=medium

  [ Sebastien Bacher ]
  * d/p/Check-for-NULL-priv-popup_window-in-gtk_combo_box_popdown.patch:
    - Check for NULL priv->popup_window in gtk_combo_box_popdown()
    (lp: #1816032)

  [ Andrea Azzarone ]
  * d/p/restore_filechooser_typeaheadfind.patch:
    - Disable typeahead if in search mode (LP: #1592177)

 -- Sebastien Bacher <email address hidden> Tue, 02 Apr 2019 17:30:09 +0200

The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.