Clock app crashes when trying to access a saved alarm

Bug #1309057 reported by Thomas Strehl on 2014-04-17
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Critical
Unassigned

Bug Description

This is on image 302. Just create some alarms, close the app, start the app again and try to edit the old alarms. In 80% of cases it crashes the app.

Changed in ubuntu-clock-app:
status: New → Confirmed
importance: Undecided → Critical
Changed in ubuntu-clock-app:
milestone: none → 2.2
Victor Thompson (vthompson) wrote :

There seems to be an issue with the AlarmModel. The following console output suggests that the model is undefined when trying to retrieve alarms from it:

file:///usr/share/click/preinstalled/com.ubuntu.clock/1.0.395/alarm/AlarmPage.qm
l:70: TypeError: Cannot read property 'enabled' of null
file:///usr/share/click/preinstalled/com.ubuntu.clock/1.0.395/alarm/AlarmList.qm
l:109: TypeError: Cannot read property 'enabled' of null
file:///usr/share/click/preinstalled/com.ubuntu.clock/1.0.395/alarm/AlarmList.qm
l:97: TypeError: Cannot read property 'enabled' of null
file:///usr/share/click/preinstalled/com.ubuntu.clock/1.0.395/alarm/AlarmList.qm
l:109: TypeError: Cannot read property 'enabled' of null
file:///usr/share/click/preinstalled/com.ubuntu.clock/1.0.395/alarm/AlarmList.qm
l:97: TypeError: Cannot read property 'enabled' of null

Changed in ubuntu-clock-app:
milestone: 2.2 → backlog
milestone: backlog → alarm-blockers
Dave Morley (davmor2) wrote :

This is still occuring in utopic r7.

It seems that you are unable to do anything with an alarm once set. The minute you touch the alarm to delete/edit the app crashes. Sometimes all it takes is opening the app and moving to the alarm tab.

JoshuaStrobl (truthfromlies) wrote :

Having this issue on r303. Clock crashes when trying to access an alarm that I've set to "once", literally 100% of the time I try to access it. Doesn't crash when I switch over to the alarm tab / page however.

Nekhelesh Ramananthan (nik90) wrote :

The issue has been identified to be EDS returning incorrect alarm status to the Alarms API which causes the Clock APP UI to crash. A fix has already been proposed for EDS. I am just waiting on that to be released to the utopic images.

David Planella (dpm) wrote :

Nekhelesh, could you use the "Link a related branch" link in the bug and add the EDS branch that contains the fix, so that we can keep track of it as part of this bug? Thanks!

Nekhelesh Ramananthan (nik90) wrote :

Here's the branch I was referring to https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-1309041/+merge/216395. I am not sure confidently if it fixes it. So let that land and i can test it.

Nekhelesh Ramananthan (nik90) wrote :

Unfortunately renato's branch https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-1309041/+merge/216395 doesn't seem to fix the issue. The clock app still crashes due to the wrong alarm status returned by EDS. However I noticed during my testing that the incorrect alarm status is only returned when editing an alarm. So while creating an alarm or opening the alarms tab everything seems fine.

Selene ToyKeeper (toykeeper) wrote :

I saw a crash like this in image Utopic 124. I created two alarms, they went off, then I went back and tried to delete them. After deleting the first alarm, the app crashed. Not 100% sure it's the same issue, but it's at least very similar.

tags: added: mako u124 ue-qa
Nekhelesh Ramananthan (nik90) wrote :

Selene, we are tracking this crash at https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1337405. It seems to be an upstream bug in the SDK.

Selene ToyKeeper (toykeeper) wrote :

FWIW, still happening on Utopic 140.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers