Menu not accessible when run via ssh xforwarding

[Reinhard Tartler]

Symptom:

When starting e.g., evince via X11 Forwarding (ssh -X), then the menu is not displayed.

Test setup:

A ubuntu/precise laptop and a ubuntu/precise workstation, both 64bit.
---
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: evince 3.4.0-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=43083bcc-3306-4670-9169-937fd10be832 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Tags: precise apparmor
Uname: Linux 3.2.0-24-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-03-03 (58 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev proxy sambashare sbuild

[Reinhard Tartler (siretart)]

apport information

[Reinhard Tartler (siretart)]

apport information

[Reinhard Tartler (siretart)]

apport information

[Reinhard Tartler (siretart)]

apport information

[Reinhard Tartler (siretart)]

I suspect this is because dbus connections are not forwarded by X11. Nevertheless, disabling the global menu would be an acceptable solution in this case.

[Sebastien Bacher (seb128)]

that's rather a gtk upstream issue, the menu hidding is done by a xsettings set by gnome-settings-daemon, that doesn't play well though with ssh forwarding

[Reinhard Tartler (siretart)]

On Di, Mai 01, 2012 at 11:16:58 (CEST), Sebastien Bacher wrote:

> that's rather a gtk upstream issue, the menu hidding is done by a
> xsettings set by gnome-settings-daemon, that doesn't play well though
> with ssh forwarding

Can you please elaborate on this? What xsetting set is responsible for
that? And how should gtk know by itself when global menus work and when
not if appmenu-gtk doesn't indicate this fact?

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

[Sebastien Bacher (seb128)]

> Can you please elaborate on this? What xsetting set is responsible for
> that? And how should gtk know by itself when global menus work and when
> not if appmenu-gtk doesn't indicate this fact?

see http://developer.gnome.org/gtk3/3.4/GtkApplicationWindow.html

"The settings "gtk-shell-shows-app-menu" and "gtk-shell-shows-menubar" tell GTK+ whether the desktop environment is showing the application menu and menubar models outside the application as part of the desktop shell. For instance, on OS X, both menus will be displayed remotely; on Windows neither will be. gnome-shell (starting with version 3.4) will display the application menu, but not the menubar. "

gtk doesn't "know by itself", gnome-settings-daemon set those properties according to the desktop environment (i.e check if you are under gnome-shell, unity, or something else by checking what dbus services are in use), one issue though is that the xsettings is for the session and will not make a difference between ssh exported and local apps ... or menu export doesn't work over ssh because they don't use the same session bus, that's a known issue, not easy to workaround though (upstream gtk wanted to avoid any roundtrip, slow or blocking check because those would lead to visual issues and menus being hidden or displayed after a delay)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[TomaszChmielewski (mangoo-wpkg)]

I'm still seeing this issue with Ubuntu 17.04.

To reproduce:

# ssh to localhost (or, any other host)
ssh -X user@localhost

# run a simple command like gedit or gnome-calculator
gedit

They run fine, unfortunately the menu is not available.

[Harald Hannelius (harald-arcada)]

I'm seeing the same problem with gnome-mines over SSH from 20.04 to 18.04.