GNOME Bugzilla – Bug 788647
Regression: No menu dropdowns via ssh x11 forwarding breaks many distros.
Last modified: 2017-10-09 14:11:27 UTC
This bug is about a newly recognized all-typical-GUI-use blocking regression mentioned on at least 6 distros. It renders gtk+ unusable via x11 ssh forwarding as no menu dropdowns appear, ever. List of affected distros at the end. gtk3-demo reproduces this. Run an X server, log in to another box that has 3.22.21 installed via ssh with forwarding enabled, in that session, run gtk3-demo. Select the 'menu' demo, click 'Run'. Choose any menu heading. Notice no options appear. Often the window will not close via the GUI X box. There is a brief flicker, many text debug entries display. 3.22.16 and per other reports possibly as late as 3.22.18 were normal. Recent Centos latest release jumped from 3.22.16 which worked to 3.22.10 which broke all users via ssh x11/forwarding. Also fails in 3.22.21 The first debug message to appear (running with debugging enabled) is: (gtk3-demo:7869): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to underallocate toplevel GtkWindow 0x2692a80. Allocation is 1x1, but minimum required size is 150x66. Many other messages follow leading to: (gtk3-demo:7869): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug This affects downstream near identical bug reports: Arch Linux: https://github.com/vim/vim/issues/1187 gvim menu items do not work on remote x11... " Reverting gtk3 to 3.20.9 fixed for now" Cgywin/X https://cygwin.com/ml/cygwin/2016-11/msg00354.html remote GTK apps nor workin correctly in Cygwin/X Redhat: https://bugzilla.redhat.com/show_bug.cgi?id=1496157 Bug 1496157 - Menus do not display over remote X11 Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1700319 GTK3 menus don't work over SSH forwarding Centos: Recent 7_4 release using 3.22.10 broke all x11 menus via forwarding, prior release used 3.16 which worked. Bug still exists in 3.22.21 Freebsd likely related re: pixbuf icon https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219143 Debian Quidlibet: https://github.com/quodlibet/quodlibet/issues/2024 Menus broken with X11 forwarding Gnome: https://bugzilla.gnome.org/show_bug.cgi?id=780101 I think it is justified to mention this in a new bug report as I believe the first was miscategorized- in many ways, not least lacking initial notice of regression and lacking initial notice of total GUI unusability among so many distros via x11/ssh, and not referring to gtkMenu widget and that so simple an app as gtk3-demo reproduces it.
What does the gtk inspector say about monitors in this situation (in the general tab) ?
Created attachment 361113 [details] snapshot of general tab of gtk inspector after failed menu click per request / comment 1
The overwritten bit was "Display localhost:11.0" Everything else is visible.
Correction: "3.22.16" above should have been "3.16.6" last known good version on centos. Reports in other distros 3.18 were correct as well.
*** Bug 770838 has been marked as a duplicate of this bug. ***
I see no reason why this was opened when Bug 780101 already existed and provided the same or more info. *** This bug has been marked as a duplicate of bug 780101 ***
It was opened for the reason stated above: In the original bug, the introductory remarks were a drop in the bucket as to the breadth and "makes linux unusable" nature of the problem. It was not clearly marked as a regression, and as such sat quietly for days -- as did all the downstream complaints/bug reports -- while people abandoned the platform. The key insight, to check the inspector noticing that somewhere between 3.16 and 3.22.10 the screen size went to 0x0, arose because of it. So it was worthwhile I think. As attention has shifted to the longer bug I'm satisfied and grateful folks are now aware of the 'blocker' nature of this as it wipes gtk3 from an entire sector of usability: x11 forwarding.
Yeah, thanks for helping to find that info. Hopefully it can finally get resolved.