Bug 1153735 - [abrt] Zim: calendar.py:366:get_date:ValueError: day is out of range for month
Summary: [abrt] Zim: calendar.py:366:get_date:ValueError: day is out of range for month
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: Zim
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robin Lee
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:ca66a61ca4438ef96d133f61f8a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-16 16:41 UTC by alex
Modified: 2015-06-30 01:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-30 01:10:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (599 bytes, text/plain)
2014-10-16 16:41 UTC, alex
no flags Details
File: environ (2.42 KB, text/plain)
2014-10-16 16:41 UTC, alex
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1382298 0 None None None Never

Description alex 2014-10-16 16:41:06 UTC
Version-Release number of selected component:
Zim-0.61-1.fc20

Additional info:
reporter:       libreport-2.2.3
cmdline:        /usr/bin/python /usr/bin/zim --ipc-server-main /tmp/zim-alex/zim-server-socket 30
executable:     /usr/bin/zim
kernel:         3.16.4-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
calendar.py:366:get_date:ValueError: day is out of range for month

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/zim/plugins/calendar.py", line 432, in on_month_changed
    for date in self.model.list_dates_for_month(self.calendar.get_date()):
  File "/usr/lib/python2.7/site-packages/zim/plugins/calendar.py", line 366, in get_date
    return datetime.date(year, month + 1, day)
ValueError: day is out of range for month

Local variables in innermost frame:
self: <Calendar object at 0x19fbcd0 (zim+plugins+calendar+Calendar at 0x1bfe590)>
year: 2014
day: 0
month: 9

Comment 1 alex 2014-10-16 16:41:08 UTC
Created attachment 947676 [details]
File: backtrace

Comment 2 alex 2014-10-16 16:41:09 UTC
Created attachment 947677 [details]
File: environ

Comment 3 Fedora End Of Life 2015-05-29 13:06:08 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-30 01:10:46 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


Note You need to log in before you can comment on or make changes to this bug.