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 603210 - Clock applet: “Set” button cancellation produces error
Clock applet: “Set” button cancellation produces error
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: clock
2.28.x
Other Linux
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-28 10:04 UTC by Martin Mai
Modified: 2020-11-06 20:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
failed (188.94 KB, image/png)
2009-11-29 15:38 UTC, Fabio Durán Verdugo 		Details

Description Martin Mai 2009-11-28 10:04:16 UTC 
Originally reported at https://bugs.edge.launchpad.net/ubuntu/+source/gnome-panel/+bug/435637:

If, in the clock applet dropdown, the user clicks “Set” on a time-zone different than the system one, it will prompt for authorization to change the system timezone.

However, If the user then clicks “Cancel”, it produces the error “Failed to set the system timezone: Not Authorized for action org.gnome.clockapplet.mechanism.settimezone” It should not display an error dialog when the user cancels the action.
Comment 1 Fabio Durán Verdugo 2009-11-29 15:38:51 UTC 
Created attachment 148691 [details]
failed

Yes, I can confirm
Comment 2 André Klapper 2009-12-18 14:14:56 UTC 
The first dialog is already complete bullshit, because it asks me for my USER password, not the ROOT password.
It does not make sense at all (I AM logged in with that password in GNOME already) and it totally fails to explain which password should be entered here (of course I first tried the root password).
This is Fedora 12.
Comment 3 André Klapper 2020-11-06 20:24:36 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.