Comment 41 for bug 321176

I don't care if the issue is in the alarm-clock, pygtk or somewhere else. The fact is that if I select Applications - Add/Remove... and search for an alarm clock I get package "alarm-clock". If I then proceed to install it and ever start it, my X session is immediately frozen. Happens on both x86_64 and i386 variants. Luckily, I know how to kill the application from another virtual terminal (I had to try killing processes until I hit alarm-clock, though...). However, an average Ubuntu user would think that the whole Ubuntu install just crashed.

Just upgrade, downgrade or remove the alarm-clock from the repositories immediately. It's clear that the software was NEVER even started during the release process of Jaunty! If *somebody* is able to successfully start and use Alarm Clock in Jaunty, then put it into the repository.