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 711780 - Gtk.ComboBox arrows are not visible the second time the menu popups
Gtk.ComboBox arrows are not visible the second time the menu popups
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkComboBox
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-11-10 14:50 UTC by Giuseppe Scrivano
Modified: 2017-08-15 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Simple reproducer (409 bytes, text/plain)
2013-11-10 15:37 UTC, Cole Robinson
Details

Description Giuseppe Scrivano 2013-11-10 14:50:41 UTC
The arrows, that helps to scroll to non visible elements in the list, disappear the second time the menu popups.  To reproduce it, click on the menu to show all the elements, leave the focus so the menu list hides; when you repeat the operation the arrows are not visible anymore.

I have attached a reproducer script.

I am using the PyGTK version available on Fedora 19 (2.24.0-7.fc19)


This bug was initially reported for virt-manager here: https://bugzilla.redhat.com/show_bug.cgi?id=1022060

In the original report, there is also a video that shows how to reproduce it on virt-manager.
Comment 1 Cole Robinson 2013-11-10 15:37:35 UTC
Created attachment 259447 [details]
Simple reproducer

Seems to be a gtk issue, here's a simple reproducer using pygobject. It launches a window with a single ComboBox with a text entry. The combo is filled with enough items to require scrolling.

First click of the combobox arrow works correctly, subsequent clicks show the rows but no scroll arrows (as demonstrated in the video reproducer in redhat bug report)
Comment 2 Cole Robinson 2013-11-10 15:42:08 UTC
(you forgot to attach a reproducer, so I jumped in :) )

Also, pygtk is the gtk2 bindings only. This bug was originally hit in virt-manager which is gtk3, so the correct bindings component is pygobject. However I think this is likely an underlying gtk3 issue.

Giuseppe can you reassign to gtk3? Doesn't look like I have permissions to do it since I didn't file the bug.
Comment 3 Giuseppe Scrivano 2013-11-11 10:14:28 UTC
reassigning to gtk3
Comment 4 Daniel Boles 2017-08-15 20:23:26 UTC
This appears to work fine in 3.22. Please reopen if you have a different test case that still breaks.