i'm confirming this bug too. i use Jaunty alpha3 fully updated running the program from commandline doesn't give something about the freeze, actually no output at all. also nothing found to the logs : .xsession-errors , /var/log/messages.
as noted to the general debug procedures https://wiki.ubuntu.com/DebuggingProgramCrash the reporter should provide : - a backtrace https://wiki.ubuntu.com/DebuggingProgramCrash - NOT attached because i haven't found any debug symbol packages (alarm-clock--dbgsym) - an strace https://wiki.ubuntu.com/Strace - i attempted to provide an strace, log attached, but i had to kill alarm-clock after that so i am not sure how valid the .log is - a valgrind https://wiki.ubuntu.com/Valgrind - i attempted to provide an Valgrind, log attached, but i had to kill Valgrind to make my desktop usable again so i am not sure how valid the .log is also running Valgrind with application's name didn't work, log attached. i had to specify full path to start it with Valgrind we certainly need some guidance here in order to provide useful bug report and feedback. please tell us how because the desktop becomes completely unusable. ** Changed in: alarm-clock (Ubuntu) Status: New => Confirmed -- [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
