doesn't send some keys to the remote computer

For the AltGr issue, there's already bug 212013.

Fix committed upstream.

Now we have an option to disable all shortcuts. Makes total sense in a VNC application.

This bug was fixed in the package vinagre - 2.23.4-1

---------------
vinagre (2.23.4-1) experimental; urgency=low

  * New upstream releases:
    - Fixes scrolling. Closes: #482564.
    - Added a gconf option to disable all menu shortcuts.
      Closes: #465606, LP: #223060.
    - Persist changes in menu shortcuts. LP: #233918.
    - Rework 'connect' and 'edit bookmark' dialogs so it's possible to
      specify options like scaling, fullscreen... LP: #205253.
    - debian/copyright: updated
    - debian/control: b-d on libpanel-applet2-dev, required for the
      new applet.
    - debian/NEWS: document the bookmark migration from
      ~/.gnome2/vinagre.bookmarks to ~/.local/share/vinagre.
  * Update Standards-Version. No changes needed.

 -- Emilio Pozuelo Monfort <email address hidden> Wed, 30 Jul 2008 21:18:35 +0100

Has trouble sending Alt-F4 to the remote computer... has the affect of closing the local Vinagre window instead, already been addressed, or do I need to open a separate bug for this trouble?

Sounds very similar to this "control-w closes the vinagre session" except I happen to be trying to send Alt-F4.

Thanks

This bug needs to be re-opened, or another one opened it its place.

Vinagre (2.24) under Intrepid is again broken due to keyboard bindings. The CTRL-ALT sequence previously used to grab the keyboard no longer works, there is no menu choice to effect the same, and keys such as a simple CTRL-d are captured by the code for a vinagre pop-up window, instead of sent downstream where they belong.

Is there some reason why we cannot provide TightVNC or similar competent VNC viewer by default instead of Vinagre? It is true that Vinegre has AVAHI support built-in, but who cares so long as basic VNC support does not function on a consistent and stable basis?

Re-opening at Noel Bergman's request.

See http://bugzilla.gnome.org/show_bug.cgi?id=555803

Noel:

That bug is fixed upstream, so presumably that means Ubuntu users will get the fix in Jaunty.

From reading the code, I have found a workaround. Run gconf-editor, and change apps->vinagre->show_accels to false. That setting is described by gconf-editor as "Set to "false" to disable menu shortcuts. Set to "true" to enable them. Note that if they are enabled, those keys will be intercepted by the menu and will not be sent to the remote host." Needless to say, having that value default to true is a very poor choice given the nature of the program. And new users are not likely to find that hidden switch without instructions.

I'll make a preferences dialog to control these settings. Will be in 2.26.

Thanks, Jonh. And please reconsider the default value. For a VNC client, it is far more important that we be able to control the remote than to have local accelerators. And Vinagre *is* my preferred VNC client when it works, which is why I get on your case when it doesn't. :-)

Scott, yes, I was simply noting that there is an upstream fix. :-)

OK, I just committed an initial preferences dialog, which allows you to control if the shortcuts (accels) exist or not. Also, I've changed its default value to FALSE, thus, vinagre doesn't have accels keys by default.

The fix will be in Vinagre 2.25.2, to be released at Dec 1st.

The fix is already present in Jaunty.

I'm having odd behavior with 2.24.2. I've tried setting the gconf pref both ways and it appears to have no effect -- the menu keys and the shortcuts all get swallowed by vinagre and not passed on.

However, if I work in full screen mode, my problems are solved -- vinagre doesn't intercept a thing (in fact, I can only get out of full screen mode by using the mouse, since F11 is passed onto the host and not swallowed by vinagre for toggling fullscreen).

Is this the design? If so, it's something people reporting this bug would benefit from knowing -- I know it saved me quite a bit of head-banging-on-desk when I discovered it (previously, I'd closed several sessions trying M-W in emacs on a remote host...).

Thomas M. Hinkle wrote:
> I'm having odd behavior with 2.24.2.

This is fixed in 2.25.x. You'll have to wait for Jaunty.

Best regards,
Emilio

The name of the option (show_accels) is unfortunate. Showing accels and enabling them are two very different things!