[X2Go-User] GTK+ pull-down menus not displayed

[Rett D. Walters]

Hi - thanks for your fast response.


On 11/08/2016 01:04 AM, Ulrich Sibiller wrote:
> On Tue, Nov 8, 2016 at 4:15 AM, Rett D. Walters <rettw78 at rtwnetwork.com> wrote:
>> I can confirm this same issue.  I have two machines running archlinux with
>> the latest updates and XFCE4, and I am seeing the exact same behavior.  I
>> have noticed that Thunar on these machines doesn't exhibit the issue but
>> just about everything else does.  Makes x2go pretty much unusable.  Also
>> have the same issue when running openbox on the x2go server, so it doesn't
>> appear to be related to the DE running on the server.  Issue appears to
>> affect Mac x2goclients as well as linux.
>>
>> It seems to have occured on one of the servers machines with the issue after
>> a recent OS update where the following packages were upgraded (I have
>> downgraded libxrender, gtk2, gtk3, to the previous versions and the problem
>> still exists, I am not sure what other packages could have this effect) :
> What version of nx-libs are you using? You could try to use a nightly
> build of nx-libs  (https://sunweavers.net/blog/node/20) and see if
> that changes anything. However, there's no nightly for Arch Linux, so
> you need to build it yourself.
Currently using 3.5.0.32-2 (archlinux package version).  I will take a 
look at upgrading this manually if all else fails.
> Otherwise try to downgrade more packages and find the one that breaks things.
>
> I would start with these:
>> upgraded libxfixes (5.0.2-1 -> 5.0.3-1)
>> upgraded mesa (12.0.2-1 -> 13.0.0-1)
>> upgraded mesa-libgl (12.0.2-1 -> 13.0.0-1)
>> upgraded pango (1.40.2-1 -> 1.40.3-1)
>> upgraded libxtst (1.2.2-1 -> 1.2.3-1)
>> upgraded gsettings-desktop-schemas (3.21.4-1 -> 3.22.0+1+g6f52ab5-1)
>> upgraded gnome-themes-standard (3.20.2-1 -> 3.22.2-1)
>> upgraded libxv (1.0.10-1 -> 1.0.11-1)
>> upgraded libxrandr (1.5.0-1 -> 1.5.1-1)
>> upgraded gtk2 (2.24.30+95+g876b5f7-1 -> 2.24.31-1)
>> upgraded gtk3 (3.20.9-1 -> 3.22.2+4+gc54f348-1)
>> upgraded xfconf (4.12.0-4 -> 4.12.1-1)
>> upgraded xfce4-panel (4.12.0-2 -> 4.12.1-1)
>> upgraded xfce4-settings (4.12.0-5 -> 4.12.1-1)
>> installed vte3 (0.46.0+5+g398a3f8-1)
>> upgraded xfce4-terminal (0.6.3-3 -> 0.8.1-1)
>> upgraded xfdesktop (4.12.3-2 -> 4.12.3-3)
I will start downgrading these suggestions to see if I can localize 
which one seems to cause the issue.  I have already downgraded several 
of them.
>>
>> upgraded wayland (1.11.0-1 -> 1.12.0-1)
> You are not using wayland, are you?
No, I am not using Wayland, however the arch packages for gtk3 and mesa 
pull in wayland as a dependency.
>> Lately whenever I launch GTK+ applications over x2go, the
>> pull-down menus are usually not displayed properly or at all.
>>
>> For example, if I launch the Xfce Terminal, I see the usual "File",
>> "Edit", "View", "Terminal", "Tabs", and "Help" labels in the pull-down
>> menu bar.  If I click on these, they become underlined as though they
>> are active, but the corresponding pull-down menu doesn't (usually)
>> appear.  Instead, a single pixel in the upper left corner of my desktop
>> turns white.  The only exception is when I click on "Help" -- the first
>> time I do this, I do get a pull-down menu, but it's attached to the
>> upper left corner of my desktop, not to the "Help" label in the Terminal
>> window. The menu is very small, though, and I need to scroll through it
>> to see all the entries.  The second or subquent times I try to view the
>> "Help" menu, I just get a single pixel.
> This sounds like a window manager problem.
>> Similar behaviour is observed in most other GTK+2 and GTK+3
>> applications, such as the GNOME Terminal and the GNOME Character Map.
>> The problem is reproducible when launhcing LibreOffice with
>> SAL_USE_VCLPLUGIN=gtk2 or SAL_USE_VCLPLUGIN=gtk3, but not with
>> SAL_USE_VCLPLUGIN=kde4 or SAL_USE_VCLPLUGIN=gen.  Some (but not all) of
>> the applications output error messages like this to the console when I
>> try to activate a pull-down menu:
>>
>> (gucharmap:26208): Gtk-CRITICAL **:
>> gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
>>
>> (gucharmap:26208): Gtk-CRITICAL **:
>> gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
>>
>> (gucharmap:26208): Gtk-CRITICAL **:
>> gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
>>
>> (gucharmap:26208): Gtk-WARNING **: Negative content width -7 (allocation 1,
>> extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
>>
>> (gucharmap:26208): Gtk-WARNING **: Negative content width -7 (allocation 1,
>> extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
> Googling for these messages leads to bugs regarding xwayland and HiDPI
> monitors, which does not fit in here (e.g.:
> https://bugs.documentfoundation.org/show_bug.cgi?id=99508), but they
> sugges using
>
> SAL_USE_VCLPLUGIN=gtk
>
> Does that help?
>
>> Anyone know what the cause might be and how I can work around it?  I'm
>> running x2goserver-4.0.1.19 on an openSUSE Tumbleweed server and
>> x2goclient-4.0.5.0 on an openSUSE 13.2 client.  The client desktop
>> environment is KDE 5.
> Have you checked if it works at all without x2go?
>
> Uli
At this time, I can confirm everything works properly on a local X 
console - this problem only occurs when using X2go to access the servers 
in question.