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 559180 - keyboard accelerator command inconsistent for application launcher properties dialog
keyboard accelerator command inconsistent for application launcher properties...
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: libpanel-applet
2.24.x
Other All
: Normal minor
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 507552 591196 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-11-03 20:40 UTC by Jason Quinn
Modified: 2010-03-08 14:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Jason Quinn 2008-11-03 20:40:48 UTC
Please describe the problem:
Depending on the "Type" of the application selected, the keyboard accelerator for the "Command" field may be different. 

Steps to reproduce:
1. Add a custom application launcher to the gnome panel.
2. Right click and bring up the properties diaglog.
3. Change the "type" of the launcher and observe the keyboard accelerator for the command field. It changes.


Actual results:
The keyboard accelerator for the command field changes.

Expected results:
It would not change.

Does this happen every time?
Yes.

Other information:
I've tested this in Ubuntu 8.04 with gnome-panel 2.22.2 and under Ubuntu 8.10 with gnome-panel 2.24.1. The problem exists on both. Note that the buttons at the bottom of the properties dialog have changed between 2.22.2 and 2.24.1 from "Help", "Revert", and "Close" to "Help", "Cancel", and "OK".
Comment 1 Vincent Untz 2009-06-18 09:11:44 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 2 Vincent Untz 2009-08-12 12:41:33 UTC
*** Bug 507552 has been marked as a duplicate of this bug. ***
Comment 3 Vincent Untz 2010-03-08 14:30:59 UTC
*** Bug 591196 has been marked as a duplicate of this bug. ***