Ubuntu
alarm-clock package

[Jaunty RC] alarm-clock package should be removed

Bug #363937 reported by Christopher Berner on 2009-04-20

This bug report is a duplicate of: Bug #321176: [Jaunty] alarm-clock causes screen to freeze. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	alarm-clock (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: alarm-clock

The current alarm-clock package is broken, and causes the entire system to become unresponsive if used. It should be removed from 9.04

This is running 9.04 RC

Steps to reproduce:
"apt-get install alarm-clock"
"alarm-clock"
observe that system is frozen.

related to bug 321176

Tags:

Christopher Berner (cberner) on 2009-04-20

tags:

added: 9.04 jaunty

Revision history for this message

Nico Bauer (oshelpdesk) wrote on 2009-04-20:

Bugs should be fixed. If you remove the package you will have the problem again with the next release. Removing the package doesn't solve the problem.

Revision history for this message

Christopher Berner (cberner) wrote on 2009-04-20:

what I meant was it should be temporarily removed, since it currently causes anyone using the alarm-clock application to have an unusable computer as soon as they upgrade to 9.04. And that bug I referenced was marked invalid, since the author of alarm-clock seems to be rewriting it in C.

Revision history for this message

Andrew (andrew-rw-robinson) wrote on 2009-04-28:

I can confirm this behavior with Jaunty on amd64 in the gnome desktop with alarm-clock version 0.9.18-3

Revision history for this message

James D. Hasselman (jhass840) wrote on 2009-04-29:

Differences between MainClass.py in versions 0.9.18-3 and 0.9.11.2 respectively Edit (52.5 KiB, text/html)

confirmed, from manually tracing the code via print statements I have determined that the problem occurs in MainClass.py on line 159 (approximately) with a call to gtk.main(). X hangs indefinitely and the call to gtk.main() never returns. The only way to kill the program is to use Ctrl+Alt+F(1, 2, or 3) and killall alarm-clock. I have heard varying assertions about the source of the problem some blaming python, others pygtk, and still others believe it is alarm clock itself. I ran a diff against MainClass.py from 0.9.18-3 and MainClass.py from 0.9.11.2 (on mint) and I came up with around 1500 lines. I'm not quite sure what to do about this although I hope a developer is watching this bug. Booting mint every night before I go to bed so that I have an alarm clock is getting old fast.

I'm attaching the file containing the diffs, hope it helps