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 588333 - time-admin, users-admin,...: "_Unlock" button displays broken mnemonic
time-admin, users-admin,...: "_Unlock" button displays broken mnemonic
Status: RESOLVED OBSOLETE
Product: gnome-system-tools
Classification: Deprecated
Component: general
2.22.x
Other All
: Normal trivial
: ---
Assigned To: Milan Bouchet-Valat
Carlos Garnacho
: 591562 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-11 21:10 UTC by Pavol Klačanský
Modified: 2009-08-19 16:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Pavol Klačanský 2009-07-11 21:10:33 UTC 
Please describe the problem:
title of unlock button is _Unclock see screenshot http://album.jabbim.cz/pk@jabbim.sk

Steps to reproduce:
1. start time-admin or users-admin
2. see bottom buttons
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Fabio Durán Verdugo 2009-07-12 02:44:51 UTC 
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.
Comment 2 Pavol Klačanský 2009-07-12 07:50:35 UTC 
I'm sorry, but I have lastest development release of GNOME (dist Ubuntu Karmic)
Comment 3 Fabio Durán Verdugo 2009-07-12 20:07:47 UTC 
what is your version of GNOME? 2.27.xx?
Comment 4 Pavol Klačanský 2009-07-13 08:22:41 UTC 
2.27.3
Comment 5 André Klapper 2009-07-13 09:39:10 UTC 
Fabio: Please check the "GNOME version" field.
Latest g-s-t release is 2.22.x.

g-s-t is unmaintained, and I am very sure that this is a duplicate.
Comment 6 Milan Bouchet-Valat 2009-07-26 10:02:43 UTC 
Pavol: Sorry for the confusion. The version you're using is actually the latest. The problem is, I can't reproduce the problem you show on the screenshot. As these buttons are likely to be provided by PolicyKit-gnome to gnome-system-tools, I suspect the problem may be in PolicyKit 1.0 that is new in Ubuntu Karmic.

Did you experience the same issue in Jaunty? The gnome-system-tools have not changed at all since then, so if the problem appeared in Karmic, it comes from elsewhere. May be worth looking in Launchpad for similar issues in other programs.
Comment 7 Pavol Klačanský 2009-07-26 19:52:13 UTC 
This issue is not in Jaunty, only Karmic
Comment 8 Milan Bouchet-Valat 2009-08-15 21:57:28 UTC 
*** Bug 591562 has been marked as a duplicate of this bug. ***
Comment 9 Milan Bouchet-Valat 2009-08-15 21:59:55 UTC 
I guess PolicyKit 1.0 has moved from using gtk_button_new_with_mnemonic() to _with_label(). As Iain Lane explained in the duplicate, bug 590656 is about changing the GTK+ default to the former, which would mean that the bug is solved in master. Please report ASAP, I'll try to check that too.
Comment 10 Milan Bouchet-Valat 2009-08-19 16:32:08 UTC 
Actually, this is now obsolete in 2.27.3 thanks to PolicyKit1, which provides us with a new PolkitLockButton to replace our button. So no need to enable mnemonics to fix that bug.