After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764784 - GtkInfoBar only shown 1st time, stays hidden forever after close
GtkInfoBar only shown 1st time, stays hidden forever after close
Status: RESOLVED DUPLICATE of bug 710888
Product: gtk+
Classification: Platform
Component: Backend: Win32
3.20.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-04-08 14:23 UTC by juloml
Modified: 2016-05-02 17:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description juloml 2016-04-08 14:23:58 UTC 
This is similar to bug 710888, however occurs independent of reveler transition state. I can only trigger issue using gtk 3.20 on MS windows. Issue was not present using GTK 3.18 on MS Windows platform. Also cannot reproduce issue using Fedora 24 (GTK 3.20.2).

Reproduction is possible using gtk3-demo-application:
1. Choose menuitem Preferences->Shapes->Square
2. Press "OK" button on info bar to hide info bar
3. Choose menuitem Preferences->Shapes->Oval

Expected result:
* GtkInfoBar shown again after step 3)

Actual result:
* info bar is not shown using GTK 3.20.2 on MS Windows
Comment 1 Ignacio Casal Quinteiro (nacho) 2016-04-08 14:38:51 UTC 
I can confirm this problem.
Comment 2 juloml 2016-04-08 14:48:34 UTC 
In case it helps.

Calling "gtk_widget_queue_resize(GTK_WIDGET(info_bar));" where gtk_widget_show is called helps as an workaround for problem.
Comment 3 LRN 2016-04-09 04:33:54 UTC 
1) I can reproduce this as well
2) I still can't believe that this is W32-specific.
3) The infobar remains "hidden" in the sense that its height remains 1px. It can be "shown" by triggering widget size re-allocation (theme change, flipping of "expand" property etc).

Since it is said to have worked in 3.18, i think the easiest way to find the culprit at the moment is to bisect between 3.18 and 3.20.[0,1,2] (whichever is earliest, i guess?). Testing with 3.19.x releases might help narrow down the bisection interval.
Comment 4 LRN 2016-04-09 15:33:49 UTC 
This bug is not present in 3.19.5, but does appear in 3.19.6.
Comment 5 LRN 2016-04-10 05:51:00 UTC 
Bisecting suggests that this bug is caused by acbff854029cc5b308c92024990abeb81355c360

That commit can't be cleanly and easily reverted, so i can't verify that it is indeed causing this bug. I'm CCing Company.
Comment 6 Cédric Bellegarde 2016-05-02 06:45:00 UTC 
Can confirm here on GTK 3.20 + X11
Comment 7 Marius Gedminas 2016-05-02 07:00:45 UTC 
Duplicate of 710888?
Comment 8 Debarshi Ray 2016-05-02 17:04:34 UTC 

*** This bug has been marked as a duplicate of bug 710888 ***