[i915] Crash when mouse at top of screen on 915GM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
X.Org X server |
Fix Released
|
High
|
|||
xserver-xorg-video-intel (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: xserver-
I am using X normally for a variable period of time - sometimes a day or more, sometimes minutes - when suddenly the screen goes blank, the backlight goes out and then comes back on (as if the X server were restarting) but then nothing appears on the screen. I cannot switch to a text terminal with C-A-F1, and C-A-Backspace does nothing. C-A-Del makes the system reboot, and very late in the process I see the splash screen signaling a reboot.
The bug occurs randomly, but I think that every time it has occurred, my mouse cursor has been at the top of the screen, just at the top of a firefox titlebar. (I have no panel across the top.) I normally have compiz turned off, but the bug also occurs when I have turned compiz on. (The attached log is from a crash with compiz active.)
Using xserver-xorg-intel 2.2.1-1ubuntu12 on 8.04; my xorg.conf contains nothing machine-specific. This did not occur with Gutsy's standard X server.
This bug resembles bug #204035 and #176377, but they are marked as closed and people encountering the same problem are urged to submit new bugs.
Changed in xserver-xorg-video-intel: | |
status: | New → Incomplete |
Changed in xserver-xorg-video-intel: | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
Changed in xorg-server: | |
status: | Unknown → Confirmed |
Changed in xorg-server: | |
status: | Confirmed → Fix Released |
Changed in xorg-server: | |
importance: | Unknown → High |
Changed in xorg-server: | |
importance: | High → Unknown |
Changed in xorg-server: | |
importance: | Unknown → High |
I have now seen the bug occur when the mouse is at the top of the screen in a non-firefox window. A cursor change occurs there, since I have no panel at the top of my screen. Could this bug be related to bug #153466?