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 684372 - Mouse selection inconsistencies on map
Mouse selection inconsistencies on map
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Date and Time
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
3.10.1
Depends on:
Blocks:
 
 
Reported: 2012-09-19 12:13 UTC by Stef Walter
Modified: 2021-06-09 16:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stef Walter 2012-09-19 12:13:07 UTC
There's various strange behavior when I use my mouse to select a timezone in the Date & Time panel. 

 * If I select the center Russian timezone (above china are two big time zones, click on the one on the left), the china timezone is highlighted instead.
 * If I click on northern Sweden, Finland is highlighted.
 * If I click on/near Moscow, an Oman and Azerbajan are highlighted, and the Moscow area is not highlighted.


Name        : control-center
Arch        : x86_64
Epoch       : 1
Version     : 3.5.91
Comment 1 Bastien Nocera 2012-09-19 12:15:10 UTC
Same bug as bug 681475?
Comment 2 Benjamin Berg 2012-09-19 13:06:22 UTC
The widget does not seem to use the fooscrollarea which is the cause of bug #681475. There also are no calls to cairo_get_path, which is the function with the bug.

I am seeing the same issues as Stef is mentioning though. The City that is sometimes not even inside the area that is marked green.

I am not sure about the northern Sweeden example, I am thinking that Stef may have selected Mariehamn, which has finish time.
However, the YEKT (Yekaterinburg) time is not correctly drawn. The area that is shown in green *does* also have UTC+6 according to wikipedia, but the area that YEKT is valid in is not shown.

The area that is shown is the same timezone as Asia/Almaty.
Comment 3 Bastien Nocera 2013-10-09 15:53:58 UTC
Still a problem in 3.10.1
Comment 4 Benjamin Berg 2017-11-26 13:44:54 UTC
Had a quick look again, I am guessing that:

1. The map is somewhat inaccurate (missing some small areas)
2. Clicking chooses the closest city and does not stop at TZ boundaries

The boundaries seem to be a static image that has not been updated for a long time now.
Comment 5 Bastien Nocera 2017-11-29 16:40:47 UTC
This is what anaconda and Ubiquity (the Fedora and Ubuntu installers, respectively) use:
https://code.launchpad.net/timezonemap

Helpfully, there's also:
https://github.com/dashea/timezonemap

This installer has the same widget but ported to Python:
https://github.com/Antergos/Cnchi

Finally, I should mention that the first timezonemap library mentioned now has the source of the map itself in SVG format.

Mathieu, what do you think of moving the timezone map widget to GNOME git, whether in the current git, or in the new gitlab instance? This would make it easier to gather all the requirements for changes, and make sure it gets ported to GTK+ 4 when the time comes.
Comment 6 Mathieu Trudel-Lapierre 2017-11-29 18:09:27 UTC
I'm not sure I'm the right person to make that kind of decision. I just happened to need to update the timezone map :)

I don't think there would be any problem as I think it should be migrated from bzr to git anyway, but others have their say as well; so I will let them chime in here. Iain may be the best person to comment.

In the meantime, there are some open merges that I'd like to review and apply if they make sense, such as https://code.launchpad.net/~dshea/timezonemap/svg-only/+merge/295631; once the open merge proposals are handled things will already be in a much nicer state to do any migration. Another update of the maps in general might not be such a bad idea either.
Comment 7 André Klapper 2021-06-09 16:28:11 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.