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 570509 - Mapping menu options to keyboard accelerators is dumb and interferes with use
Mapping menu options to keyboard accelerators is dumb and interferes with use
Status: RESOLVED DUPLICATE of bug 485317
Product: vinagre
Classification: Applications
Component: general
0.5.x
Other All
: Normal normal
: ---
Assigned To: vinagre-maint
vinagre-maint
Depends on:
Blocks:
 
 
Reported: 2009-02-04 16:20 UTC by paul
Modified: 2009-02-04 16:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description paul 2009-02-04 16:20:33 UTC
Please describe the problem:
Mapping control+D to a "Add Bookmarks" function was confusing, and prevents me from sending an end of file to the remote computer.

Steps to reproduce:
1. Connect to a unix machine
2. Try to send a control D
3. Watch in anger as the command doesn't get sent, search the help screen and find absolutely no useful documentation as to how to override it. The Control+N mapping also prevents me from using that keystroke on the remote computer too. 


Actual results:
Anger and Frustration

Expected results:
The same thing every VNC client does, send the keystroke unaltered.

Does this happen every time?
Unfortunately yes.

Other information:
Keyboard accelerators are not needed in this application. I never need a more handy way to "Add a bookmark", and probably don't need anything handy to connect to a new computer either. The use of these keys in particular is ridiculous. If you're going to map something, choose combinations that don't interfere with use, like control+alt+F8 or something uncommon.
Comment 1 Jonh Wendell 2009-02-04 16:43:10 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 485317 ***