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 603179 - year 0 shouldn't exist in calendar
year 0 shouldn't exist in calendar
Status: RESOLVED DUPLICATE of bug 166465
Product: gtk+
Classification: Platform
Component: Widget: GtkCalendar
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-11-27 19:13 UTC by Martin Mai
Modified: 2013-10-17 07:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Martin Mai 2009-11-27 19:13:37 UTC
Originally reported at https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/421461:

I notice that in the gnome clock, there is the year 0. It shouldn't exist in the calendar.


The year zero just doesn't exist: http://en.wikipedia.org/wiki/Year_zero
Comment 1 André Klapper 2009-12-10 21:50:00 UTC
Please always provide exact steps to reproduce and the version used.
==> NEEDINFO.
Comment 2 Martin Mai 2009-12-11 14:27:00 UTC
The steps seemed self explanatory. If you click on the calendar applet in the gnome-panel, you can switch between the years by clicking on the arrows next to the year (At the moment that is "2009").

The launchpad bug is about the fact that you are able to choose the year 0 (zero). Which shouldn't be the case, when looking at the Wikipedia article:
>>>
"Year zero is not used in the widely used Gregorian calendar, nor in its predecessor, the Julian calendar. Under those systems, the year 1 BC is followed by AD 1. [...]"
<<<

Version is 2.28.0.
Comment 3 André Klapper 2009-12-14 17:34:28 UTC
(In reply to comment #2)
> If you click on the calendar applet in the gnome-panel, you can switch between 
> the years by clicking on the arrows next to the year (At the moment that is 
> "2009").

And you clicked 2008 times to find this bug, or how can I reproduce?
Comment 4 Martin Mai 2009-12-14 17:54:58 UTC
I didn't find this bug (the reporter at launchpad did), but I could reproduce it as you say by clicking 2008 times (or holding down the mouse button for some time).
Comment 5 André Klapper 2009-12-14 17:56:45 UTC
Heh. :-)
I'm missing a usecase here and propose WONTFIX.
Comment 6 Martin Mai 2009-12-14 18:30:13 UTC
Well, the original reporter says >>>it's not really a "problem"...<<< (That's why I set it to "minor"). It might be kind of amusing that someone figured it out and I will leave it to you whether it is worth to be fixed in any way. Regards.
Comment 7 kidanger 2009-12-27 10:20:28 UTC
To find this "bug" I made a little python script, like this:

import os
while 1:
   os.system("xdotool click 1")

Then move the cursor to the calendar applet. 
(That a not-clean solution, but it works...)

Thanks.
Comment 8 Timothy Arceri 2013-10-17 07:26:05 UTC

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