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 591562 - "Unlock" button has "_Unlock" as the text
"Unlock" button has "_Unlock" as the text
Status: RESOLVED DUPLICATE of bug 588333
Product: gnome-system-tools
Classification: Deprecated
Component: users-admin
2.27.x
Other All
: Normal trivial
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2009-08-12 13:22 UTC by Iain Lane
Modified: 2009-08-15 21:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28

Attachments
Changed "_Unlock" to "Unlock" (978 bytes, patch)
2009-08-13 19:44 UTC, Kyle Pelton 		none Details | Review

Description Iain Lane 2009-08-12 13:22:44 UTC 
Please describe the problem:
This bug was reported as [0]:

"Subject says it all. See screenshot[1]."

[0] https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/412507
[1] http://launchpadlibrarian.net/30222957/Screenshot-Users%20Settings.png

Steps to reproduce:
1. Open users-admin
2. Look at the unlock button


Actual results:
Text is "_Unlock"

Expected results:
Text should be "Unlock"

Does this happen every time?
yes

Other information:
Grep analysis reports that the problem is here:

src/common/gst-dialog.c:	priv->polkit_button = gst_polkit_button_new (NULL, _("_Unlock"));
Comment 1 Kyle Pelton 2009-08-13 19:44:36 UTC 
Created attachment 140696 [details] [review]
Changed "_Unlock" to "Unlock"
Comment 2 André Klapper 2009-08-13 22:51:18 UTC 
That's not a proper fix as the _ is meant as a mnemonic. Probably you have to wrap the function call instead.
Comment 3 Iain Lane 2009-08-13 23:10:08 UTC 
This is probably related to #590656 and so might be fixed in master
Comment 4 Milan Bouchet-Valat 2009-08-15 21:57:28 UTC 
Thanks for reporting and posting a patch. However, as André and Iain have pointed out, the fix for that problem should be done elsewhere in the system. Anyway, that's a duplicate of bug 588333, and I'll continue the discussion there.

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