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 606096 - evolution meeting invitation has duplicate keyboard shortcuts
evolution meeting invitation has duplicate keyboard shortcuts
Status: RESOLVED DUPLICATE of bug 603682
Product: evolution
Classification: Applications
Component: Calendar
2.28.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-01-05 12:06 UTC by Pedro Villavicencio
Modified: 2010-01-06 04:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Pedro Villavicencio 2010-01-05 12:06:30 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/499418

"Steps to reproduce:

1) Go to calendar view (Control+3)
2) Right-click and select "New Meeting"
3) Observe that to the right of the "Attendee" box are 3 buttons: Add, Remove and Edit.
4) Further observe that the shortcut for "Add" is "Alt+A" (the "A" of "Add" being underlined).
5) Finally, observe that the shortcut for "Show Attachment Bar" is *also* "Alt+A"
    ("A" of "Attachment" is underlined).

This is a bug since in Jaunty you could bring up the meeting window, hit Alt+A and start typing a persons email address into the Attendee box. In Karmic, you end up highlighting the attachment bar."

Thanks,
Comment 1 Fabio Durán Verdugo 2010-01-05 12:43:48 UTC 
I can confirm this.
Comment 2 Akhil Laddha 2010-01-06 04:17:04 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 bug 603682 ***