As I've told before, this isn't Alarm Clock's fault. Why? Because this is written in Python and from Python side I can't even manage memory to crash like this. There is a bug in Python binding to some library in new Ubuntu (I know because it crashes for me too).
The only way to manage memory is to use Python's garbage collector which won't cause crash like this. /var/lib/python-support/python2.6/gtk-2.0/gtk/_gtk.so[0x7f6fbf7218e0] This line tells that it's because of broken GTK binding for Python in Ubuntu 8.10. If Python code can crash C library it's not the Python application's bug but security issue in Python or Python binding for some library - Python is only a scripting language just like perl or php. It seems like a bug in PyGTK. As I said, it crashes right after starting the thread system. -- [Jaunty] alarm-clock causes screen to freeze https://bugs.launchpad.net/bugs/321176 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
