Clock freezes seconds after load

Bug #1276167 reported by Michael Hall
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Invalid
Undecided
Unassigned
qtorganizer5-eds (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After loading the clock app, within a few seconds during which it is responsive, the whole things freezes, and the following is repeatedly written to the app's log:

libecal-CRITICAL **:
               time_days_in_month: assertion 'year >= 1900' failed

I used to have saved Alarms, and I also have saved Event data (from calendar/syncevolution) one or more of which may be causing this problem when the app tries to load them.

Tags: avengers
affects: qtorganizer5-eds → qtorganizer5-eds (Ubuntu)
Revision history for this message
Michael Hall (mhall119) wrote :

Deleting items out of the 'Alarms' database in EDS prevents the freeze and errors

Changed in qtorganizer5-eds (Ubuntu):
status: New → Invalid
Changed in ubuntu-clock-app:
status: Confirmed → Invalid
milestone: none → 1.8
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.