[Jaunty] alarm-clock causes screen to freeze
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Automate |
Invalid
|
Undecided
|
Unassigned | ||
PyGTK |
Invalid
|
Undecided
|
Unassigned | ||
Ubuntu |
Invalid
|
Low
|
Unassigned | ||
Jaunty |
Invalid
|
Low
|
Unassigned | ||
alarm-clock (Ubuntu) |
Fix Released
|
High
|
Scott Kitterman | ||
Jaunty |
Fix Released
|
High
|
Unassigned | ||
python2.6 (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1. launch alarm-clock
What happens:
Image on the screen becomes frozen. Mouse pointer is moving, but if I'm clicking on something, I cannot see any reaction (however, there is a reaction, because if I'm trying to launch a program, I am able to see it after switching to terminal by ctrl-alt-f1 and running ps aux). It happens both with compiz and with metacity.
ii xserver-xorg-core 2:1.5.99.
ii xserver-
ii alarm-clock 0.9.18-2
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
stetzen@
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) 965GM GEM 20090114 x86/MMX/SSE2
TEST CASE:
Start alarm-clock, watch your system hang.
Reset the system.
Install the updated package.
Start alarm-clock, watch your system not hang.
Changed in alarm-clock (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in alarmclock: | |
status: | New → Invalid |
Changed in alarm-clock (Ubuntu): | |
assignee: | nobody → Scott Kitterman (kitterman) |
importance: | Undecided → High |
status: | Confirmed → In Progress |
tags: |
added: verification-done removed: verification-needed |
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/DebuggingPr ogramCrash /wiki.ubuntu. com/DebuggingPr ogramCrash - NOT attached because i haven't found any debug symbol packages (alarm- clock-- dbgsym) /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 /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
the reporter should provide :
- a backtrace https:/
- an strace https:/
- a valgrind https:/
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.