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 687985 - clock showing wrong month when clicked
clock showing wrong month when clicked
Status: RESOLVED DUPLICATE of bug 681325
Product: gnome-panel
Classification: Other
Component: clock
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-11-09 13:18 UTC by left
Modified: 2012-11-12 12:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description left 2012-11-09 13:18:57 UTC
When I click on the clock applet the calender appears showing the month of December. It's the 9th of November. 

Changing month and/or day of the year shows the same problem. When clicked the calender shows the next month and not the current. 

In this wrong month showed the (correct) day gets highlighted, like it was reported on bug 565200, so that you think the calender is showing the current month with the current day highlighted, when actually it's not.


gnome-panel 3.6.0-1






+++ This bug was initially created as a clone of Bug #565200 +++

When you click on the clock, a calendar of the month drops down, with the current day-of-month highlighted. When you change the month or year that is displayed, the same day-of-month stays highlighted, which doesn't make much sense: If it's 20 Dec. today and I scroll to January, 20 January does not have any special significance.
Comment 1 Vincent Untz 2012-11-12 09:22:56 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 681325 ***
Comment 2 left 2012-11-12 12:30:46 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> This particular bug has already been reported into our bug tracking system, but
> we are happy to tell you that the problem has already been fixed. It should be
> solved in the next software version. You may want to check for a software
> upgrade.
> 
> *** This bug has been marked as a duplicate of bug 681325 ***


Sorry, I'had not found that it was already been reported. Thanks for your time.